Package org.geotools.data.geoparquet

Class GeoParquetDataStoreFactory

  • All Implemented Interfaces:
    DataAccessFactory, DataStoreFactorySpi, Factory
    public class GeoParquetDataStoreFactory
extends ForwardingDataStoreFactory<GeoParquetDataStoreFactoryDelegate>
implements DataStoreFactorySpi
    DataStoreFactory for GeoParquet files, powered by DuckDB.

    This factory creates DataStore instances that can read and query GeoParquet format files, both local and remote. GeoParquet is an open format for geospatial data that builds on the Apache Parquet columnar storage format, providing efficient access to large geospatial datasets.

    The implementation uses DuckDB and its extensions (spatial, parquet, httpfs) to handle the heavy lifting of reading and querying Parquet files. This provides excellent performance and compatibility with various storage backends including local files, HTTP/HTTPS, and S3.

    Usage example: 

    
 Map<String, Object> params = new HashMap<>();
 params.put("dbtype", "geoparquet");
 params.put("uri", "file:/path/to/data.parquet");

 DataStore store = DataStoreFinder.getDataStore(params);

    • Constructor Detail

      • GeoParquetDataStoreFactory

        public GeoParquetDataStoreFactory()

    • Method Detail

      • createDataStore

        public GeoparquetDataStore createDataStore​(Map<String,​?> params)
                                    throws IOException
        Description copied from interface: DataStoreFactorySpi
        Construct a live data source using the params specifed.

        You can think of this as setting up a connection to the back end data source.

        Magic Params: the following params are magic and are honoured by convention by the GeoServer and uDig application.

        • "user": is taken to be the user name
        • "passwd": is taken to be the password
        • "namespace": is taken to be the namespace prefix (and will be kept in sync with GeoServer namespace management.
        When we eventually move over to the use of OpperationalParam we will have to find someway to codify this convention.
        Specified by:
        createDataStore in interface DataAccessFactory
        Specified by:
        createDataStore in interface DataStoreFactorySpi
        Overrides:
        createDataStore in class ForwardingDataStoreFactory<GeoParquetDataStoreFactoryDelegate>
        Parameters:
        params - The full set of information needed to construct a live data store. Typical key values for the map include: url - location of a resource, used by file reading datasources. dbtype - the type of the database to connect to, e.g. postgis, mysql
        Returns:
        The created DataStore, this may be null if the required resource was not found or if insufficent parameters were given. Note that canProcess() should have returned false if the problem is to do with insuficent parameters.
        Throws:
        IOException - if there were any problems setting up (creating or connecting) the datasource.