Skip to content
Permalink
Browse files

sipify them all…

… oh there is only 2
  • Loading branch information
3nids committed Jul 9, 2020
1 parent ca89fdf commit 3fdbfe36022fffc9677f73c423b2a1af8e9777d1
@@ -29,8 +29,10 @@ yet support editing transactions.
The main data providers supported by QGIS are listed below.

\section mesh_providers Mesh data providers
\------------------------------------------

\subsection mesh_memory Memory data providerType (mesh_memory)
\~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The memory data provider is used to construct in memory data, for example scratch
data. There is no inherent persistent storage of the data. The data source uri is constructed.
@@ -53,6 +55,7 @@ E.g. to create mesh with one quad and one triangle
QgsMeshLayer *scratchLayer = new QgsMeshLayer(uri, "My Scratch layer", "mesh_memory");

\subsection mdal MDAL data provider (mdal)
\~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Accesses data using the MDAL drivers (https://github.com/lutraconsulting/MDAL). The url
is the MDAL connection string. QGIS must be built with MDAL support to allow this provider.
@@ -42,8 +42,10 @@ Sample usage of the QgsVectorLayer class:
The main data providers supported by QGIS are listed below.

\section providers Vector data providers
\---------------------------------------

\subsection memory Memory data providerType (memory)
\~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The memory data provider is used to construct in memory data, for example scratch
data or data generated from spatial operations such as contouring. There is no
@@ -71,6 +73,7 @@ trigger such warning, it is possible to suppress that by setting the following c
layer.setCustomProperty("skipMemoryLayersCheck", 1)

\subsection ogr OGR data provider (ogr)
\~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Accesses data using the OGR drivers (http://www.gdal.org/ogr/ogr_formats.html). The url
is the OGR connection string. A wide variety of data formats can be accessed using this
@@ -79,24 +82,28 @@ web services. Some of these formats are also supported by custom data providers
below.

\subsection spatialite SpatiaLite data provider (spatialite)
\~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Access data in a SpatiaLite database. The url defines the connection parameters, table,
geometry column, and other attributes. The url can be constructed using the
QgsDataSourceUri class.

\subsection postgres PostgreSQL data provider (postgres)
\~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Connects to a PostgreSQL database. The url defines the connection parameters, table,
geometry column, and other attributes. The url can be constructed using the
QgsDataSourceUri class.

\subsection mssql Microsoft SQL server data provider (mssql)
\~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Connects to a Microsoft SQL server database. The url defines the connection parameters, table,
geometry column, and other attributes. The url can be constructed using the
QgsDataSourceUri class.

\subsection wfs WFS (web feature service) data provider (wfs)
\~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Used to access data provided by a web feature service.

@@ -130,6 +137,7 @@ spatial binary operators and the QGIS local “geomFromWKT, geomFromGML”
geometry constructor functions.

\subsection oapif OGC API - Features data provider (oapif)
\~~~~~~~~~~~~~~~~~~~~~~~~~-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Used to access data provided by a OGC API - Features server.

@@ -155,6 +163,7 @@ Also note:
into the spatial binary operators e.g intersects($geometry, geomFromWKT('POINT (5 6)'))

\subsection delimitedtext Delimited text file data provider (delimitedtext)
\~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Accesses data in a delimited text file, for example CSV files generated by
spreadsheets. The contents of the file are split into columns based on specified
@@ -301,6 +310,7 @@ Errors encountered loading the file will not be reported in a user dialog if
quiet is included (They will still be shown in the output log).

\subsection gpx GPX data provider (gpx)
\~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Provider reads tracks, routes, and waypoints from a GPX file. The url
defines the name of the file, and the type of data to retrieve from it
@@ -309,6 +319,7 @@ defines the name of the file, and the type of data to retrieve from it
An example url is "/home/user/data/holiday.gpx?type=route"

\subsection grass Grass data provider (grass)
\~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Provider to display vector data in a GRASS GIS layer.

0 comments on commit 3fdbfe3

Please sign in to comment.
You can’t perform that action at this time.