semvec/pypi-packages huggingface dataset:
markdown-site-utils 0.2.2
Some utilities for managing Markdown files with metadata.
License: MIT
Requires Python: >=3.11,<4.0

# Markdown Site Utils

Some utilities for managing Markdown files with metadata.

The notion is that a content-oriented website may be written as a 
hierarchical series of Markdown files (with an ".md" extension) underneath
some data directory, e.g.:

    DATA_DIR/
      index.md
      foo.md
      bar.md
      subdir/
        index.md
        foo.md
        bar.md

Each file may contain metadata, written in TOML in a section at
the top, bounded by '+++' lines:

    +++
    title = "My Page Title"
    +++

    # Some Markdown

YAML and JSON may also be used. YAML blocks should start and end with lines
consisting of three dashes; JSON blocks should consist of a single JSON object
with opening and closing braces on lines by themselves. The data block is optional
but if present must begin on the first line of the file.

To use the library, you get create an `mdsite.DB` object with the path to your
data directory:

    mydb = mdsite.DB("/path/to/data/dir")

Then call `get_data(path)` for the path into the directory you want, leaving
out the `.md` filename suffix, and, if you are looking for an index file, leaving
out `index.md`:

    data = mydb.get_data("/node/leaf")

The above gets data for `$DATA_DIR/node/leaf.md`, or for
`$DATA_DIR/node/leaf/index.md`, if that file exists instead. 

The library also supports hierarchical configuration, also written in TOML,
YAML, or JSON, stored in files called `config.{toml,yaml,json}` depending on the
config language employed.
keops-vt 1.0.0
CLI tool for custom edition and management of Mapbox Vector Tiles in MBTiles format
License: MIT
Requires Python: >=3.7
Keywords: mbtiles,python,vector-tiles

# Keops
[![Project Status: Active – The project has reached a stable, usable state and is being actively developed.](https://www.repostatus.org/badges/latest/active.svg)](https://www.repostatus.org/#wip)
![CI](https://github.com/fmariv/keops-vt/actions/workflows/test_lint.yaml/badge.svg)

<p align="center">
    <img src="favicon.png" alt="Keops logo">
</p>

Keops is a CLI tool that allows you to apply some logic to vector tiles in a MBTiles file, such as removing or getting the size of a given tile, obtaining the vector layers that conform the MBTiles or shrinking the vector data, in order to reduce the data size.

Read the full documentation for more details: [keops.franmartin.es](https://keops.franmartin.es/).

## Installation

Keops needs Python 3.7 or higher. The recommended way to install it is via [pip](https://pypi.org/project/keops-tiles/).

``` 
pip install keops-vt
```

If you want to run the ```shrink``` command you also need [Docker](https://www.docker.com/).

## CLI Usage

The usage is pretty simple and straigthforward. For instance, if you want to drop a given tile in a MBTiles:

```bash
keops erase input.mbtiles 6/10/23
```

Keops have some more functionalities. To check them, simply execute ```keops``` or ```keops --help``` in your bash.

```bash
Usage: keops [OPTIONS] COMMAND [ARGS]...

  Keops command line interface

Options:
  --help  Show this message and exit.
 
Commands:
  debug   Debug a MBTiles file: get info related with layers and their
          features in a given MBTiles
  erase   Erase a tile in a MBTiles file
  info    Extract and print the metadata info from a MBTiles file
  shrink  Reduce and simplify all features of all or any vector tiles in a
          MBTiles container. Docker required.
  size    Get the size of a given tile or zoom level in a MBTiles file


```

## Roadmap

If you are interested on the roadmap of the project, check the [ROADMAP](ROADMAP.md) file.

## License
This project is licensed under the MIT License - see the [LICENSE](LICENSE.md) file for details.

## Credits

The merit of the shrink module belongs entirely to [rastapasta](https://github.com/rastapasta/tileshrink), as the unique developer of tileshrink,
and [ooZberg](https://github.com/ooZberg), as the person who wrapped it in a Docker image in order to use it without worrying
about the Node.js version. What I have done is creating a backup of the Docker image and 
wrapping it again in this package, so it can be used in a focused environment.