Package com.massifmaps.datasources


package com.massifmaps.datasources
  • Class
    Description
    A tile data source where each map tile is a seperate image file bundled with the application.
    The requests are generated using a template scheme, where tags in the basePath string are replaced with actual values.
    The following tags are supported: zoom, x, y, xflipped, yflipped, quadkey.

    For example, if basePath = "t{zoom}_{x}_{y}.png" and the requested tile has zoom == 2,
    x == 1 and y == 3, then the tile will be loaded from the following path: "t2_1_2.png".
    Tile data source that uses given bitmap with two, three or four control points define a raster overlay.
    Note: if two points are given, conformal transformation is calculated.
    A tile data source that loads tiles from another tile data source and caches them.
    A tile data source that combines two data sources (usually offline and online) and selects tiles
    based on zoom level.
    A tile data source that generates vector contour lines on the fly from an
    RGB-encoded elevation (DEM) tile data source.
    A tile data source that builds vector tiles from GeoJSON inputs.
    A tile data source that loads tiles using a HTTP connection.
    The requests are generated using a template scheme, where tags in the baseURL string are replaced with actual values.
    The following tags are supported: s, z, zoom, x, y, xflipped, yflipped, quadkey, frame.

    For example, if baseURL = "https://tile.openstreetmap.org/{zoom}/{x}/{y}.png" and the requested tile has zoom = 2,
    x = 1 and y = 3, then the tile will be loaded from the following URL: "https://tile.openstreetmap.org/2/1/3.png".

    This data source also supports PMTiles archives hosted over HTTP.
    Spatial index type for local data source.
    The accepted values of this constant namespace.
    A modifiable vector data source that keeps all the elements in the local memory.
    Optionally vector elements can be kept in a spatial index and only the visible elements get rendered.
    There can be a small delay before previously invisible elements become visible after view changes.
    This makes it suitable for cases where there are a large number of static vector elements.

    The draw order of vector elements within the data source is undefined.
    An online tile data source that connects to MapTiler Cloud tile server.
    This data source should be used with vector tiles,
    though by customizing service URL could be used with raster tiles also.
    Be sure to read the Terms and Conditions of your MapTiler service provider to see if the
    service is available for your application.
    Note: this class is experimental and may change or even be removed in future SDK versions.
    MBTiles tile schemes.
    The accepted values of this constant namespace.
    A tile data source that loads tiles from a local Sqlite database.
    The database must contain table "tiles" with the following fields:
    "zoom_level" (tile zoom level), "tile_column" (tile x coordinate),
    "tile_row" (tile y coordinate), "tile_data" (compressed tile image).
    A tile data source that loads tiles from another tile data source
    and caches them in memory.
    A tile data source that merges two MBVT/protobuf data sources into one.
    It is assumed that the layer ids from the two sources are distinct.
    A tile data source that handles multiple data sources.
    A tile data source that combines two data sources (usually offline and online).
    All requests are made first to first data source.
    A tile data source that loads tiles from package manager.
    A tile data source that loads tiles from another tile data source
    and caches them in an offline sqlite database.
    A tile data source that loads tiles from a PMTiles v3 archive file.
    PMTiles is a single-file archive format for pyramids of tiled data.
    The archive format supports efficient random access and metadata storage.
     
    Abstract base class for tile data sources.
    What a tile download reports, as one object.

    A listener has four callbacks with four different arguments; a facade event carries a payload,
    and one payload class over the four is what lets a binding subscribe to "the download" rather
    than to each of them.
    Listener for tile downloader.
    Abstract base class for envelope based vector data sources.