parseo 0.4.4__py3-none-any.whl

parseo/template.py

@@ -0,0 +1,78 @@
+from __future__ import annotations
+
+import re
+from typing import Dict
+from typing import List
+from typing import Tuple
+from typing import Union
+
+def _field_regex(spec: Union[Dict, None]) -> str:
+    """Return a regex for a field spec.
+
+    If *spec* is missing or empty, a permissive pattern ``.+`` is used.
+    Anchors in patterns are stripped so they integrate into larger regexes.
+    """
+    if not spec:
+        return ".+"
+    if "enum" in spec:
+        return "(?:" + "|".join(re.escape(v) for v in spec["enum"]) + ")"
+    if "oneOf" in spec:
+        options = [
+            _field_regex(option)
+            for option in spec["oneOf"]
+            if option is not None
+        ]
+        if not options:
+            return ".+"
+        return "(?:" + "|".join(f"(?:{option})" for option in options) + ")"
+    pattern = spec.get("pattern")
+    if pattern is None:
+        raise KeyError("Field spec missing 'pattern' or 'enum'")
+    if pattern.startswith("^"):
+        pattern = pattern[1:]
+    if pattern.endswith("$"):
+        pattern = pattern[:-1]
+    return pattern
+
+def compile_template(template: str, fields: Dict[str, Dict]) -> Tuple[str, List[str]]:
+    """Compile *template* into a regex pattern and extract field order.
+
+    ``{field}`` placeholders are replaced using patterns or enums from
+    *fields*. Optional segments can be denoted with ``[ ... ]`` and will be
+    converted into non-capturing optional groups. The returned pattern is
+    anchored with ``^`` and ``$``.
+    """
+    order: List[str] = []
+
+    def _compile(segment: str) -> str:
+        result = ""
+        i = 0
+        while i < len(segment):
+            ch = segment[i]
+            if ch == "{":
+                j = segment.index("}", i)
+                name = segment[i + 1 : j]
+                if name not in order:
+                    order.append(name)
+                regex = _field_regex(fields.get(name))
+                result += f"(?P<{name}>{regex})"
+                i = j + 1
+            elif ch == "[":
+                depth = 1
+                j = i + 1
+                while j < len(segment) and depth:
+                    if segment[j] == "[":
+                        depth += 1
+                    elif segment[j] == "]":
+                        depth -= 1
+                    j += 1
+                inner = segment[i + 1 : j - 1]
+                result += f"(?:{_compile(inner)})?"
+                i = j
+            else:
+                result += re.escape(ch)
+                i += 1
+        return result
+
+    pattern = "^" + _compile(template) + "$"
+    return pattern, order

parseo-0.4.4.dist-info/METADATA

@@ -0,0 +1,402 @@
+Metadata-Version: 2.4
+Name: parseo
+Version: 0.4.4
+Summary: Filename parser/assembler for satellite data
+Author-email: Matteo Mattiuzzi <matteo@mattiuzzi.com>
+License: EUPL-1.2
+Project-URL: Homepage, https://github.com/copernicus-land/parsEO
+Project-URL: Repository, https://github.com/copernicus-land/parsEO.git
+Project-URL: Issues, https://github.com/copernicus-land/parsEO/issues
+Project-URL: Changelog, https://github.com/copernicus-land/parsEO/releases
+Keywords: satellite,remote-sensing,filenames,sentinel,parsing
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Science/Research
+Classifier: License :: OSI Approved :: European Union Public Licence 1.2 (EUPL 1.2)
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Operating System :: OS Independent
+Classifier: Topic :: Scientific/Engineering :: GIS
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE.txt
+Requires-Dist: build>=1.4.4
+Provides-Extra: dev
+Requires-Dist: build; extra == "dev"
+Requires-Dist: twine; extra == "dev"
+Requires-Dist: ruff; extra == "dev"
+Requires-Dist: mypy; extra == "dev"
+Requires-Dist: pytest; extra == "dev"
+Requires-Dist: pytest-cov; extra == "dev"
+Provides-Extra: web
+Requires-Dist: fastapi; extra == "web"
+Requires-Dist: uvicorn; extra == "web"
+Dynamic: license-file
+
+::: {align="center"}
+# parsEO
+
+**parsEO** is a Python toolkit that parses existing Earth Observation filenames into structured metadata and assembles new filenames from validated fields. Filename rules live in JSON schemas, turning the repository into a single source of truth for product nomenclature.
+:::
+
+## Why parsEO?
+
+-   **Bidirectional workflows** – convert filenames to Python dictionaries and rebuild filenames from the same fields.
+-   **Schema-driven** – JSON schemas define every product token, validation rule, and STAC link. Drop in a new schema file and it is discovered automatically.
+-   **Extensible** – contributions focus on data, not glue code. Adding support for a new mission only requires a schema.
+
+## Supported product families
+
+-   **Sentinel missions** – S1, S2, S3, S4, S5P, S6
+-   **Landsat** – LT04, LT05, LE07, LC08, LC09
+-   **NASA MODIS** – Terra and Aqua MODIS products
+-   **EUMETSAT missions** – MTG, Metop
+-   **Copernicus Land Monitoring Service (CLMS)**
+    -   Corine Land Cover (CLC) and CLC+ Raster
+    -   European Ground Motion Service (EGMS) Level 2 basic/calibrated products, Level 3 velocity grid, and GNSS model
+    -   Urban Atlas Land Cover / Land Use
+    -   High Resolution Vegetation Phenology & Productivity (HR-VPP): Seasonal Trajectories (PPI) and Vegetation Indices (FAPAR, LAI, NDVI, PPI, FCOVER, DMP)
+    -   High Resolution Water & Snow / Ice (HR-WSI): CC, FSC, GFSC, ICD, SWS, WDS, WIC, WIC-COMB, SP_S2, SP_COMB
+    -   High Resolution Layers (HRL): Forest Type, Grassland, Imperviousness, Non-Vegetated Land Cover Characteristics, Tree Cover Density, Water & Wetness, Small Woody Features
+
+## Installation
+
+``` bash
+pip install parseo
+```
+
+For development installs:
+
+``` bash
+git clone https://github.com/copernicus-land/parsEO.git
+cd parsEO
+pip install -e .
+```
+
+Confirm the CLI is available:
+
+``` bash
+parseo --version
+```
+
+## Quick start
+
+### Parse a filename
+
+``` python
+from parseo import parse_auto
+
+name = "S2B_MSIL2A_20241123T224759_N0511_R101_T03VUL_20241123T230829.SAFE"
+result = parse_auto(name)
+
+print(result.valid)   # True
+print(result.fields)  # structured dict of extracted fields
+```
+
+Another example using a MODIS filename:
+
+``` python
+from parseo import parse_auto
+
+name = "MOD09GA.A2021123.h18v04.006.2021132234506.hdf"
+result = parse_auto(name)
+
+print(result.fields["platform"])  # MOD
+print(result.fields["product"])   # 09
+print(result.fields["variant"])   # GA
+```
+
+The MODIS schema advertises the Processing, Sat, Raster, and Electro-Optical STAC extensions, enabling automated STAC metadata generation (`processing`, `sat`, `raster`, `eo`).
+
+### Assemble a filename
+
+``` python
+from parseo import assemble, assemble_auto
+
+fields = {
+    "platform": "S2B",
+    "instrument": "MSI",
+    "processing_level": "L2A",
+    "sensing_datetime": "20241123T224759",
+    "processing_baseline": "N0511",
+    "relative_orbit": "R101",
+    "tile_id": "T03VUL",  # MGRS tile (TxxYYY, e.g. T32TNS)
+    "generation_datetime": "20241123T230829",
+    "extension": "SAFE",
+}
+
+assemble_auto(fields)
+# 'S2B_MSIL2A_20241123T224759_N0511_R101_T03VUL_20241123T230829.SAFE'
+
+assemble(fields, family="S2")
+# Uses the default (current) Sentinel-2 schema for quicker resolution.
+
+assemble(fields, family="S2", version="1.0.0")
+# Lock both family and schema version explicitly.
+```
+
+To force a specific schema file:
+
+``` python
+from pathlib import Path
+from parseo import assemble
+
+schema_path = Path("src/parseo/schemas/copernicus/sentinel/s2/s2_filename_v1_0_0.json")
+filename = assemble(fields, schema_path=schema_path)
+```
+
+`parse_auto` reports the schema version and lifecycle status that were used:
+
+``` python
+from parseo import parse_auto
+
+result = parse_auto("S2B_MSIL2A_20241123T224759_N0511_R101_T03VUL_20241123T230829.SAFE")
+print(result.version)  # '1.0.0'
+print(result.status)   # 'current'
+```
+
+### Command-line interface
+
+The same functionality is exposed through the CLI.
+
+``` bash
+# Parse a filename
+parseo parse S2B_MSIL2A_20241123T224759_N0511_R101_T03VUL_20241123T230829.SAFE
+
+# Parse a Copernicus Land Monitoring Service (CLMS) filename
+parseo parse ST_20240101T123045_S2_E15N45-03035-010m_V100_PPI.tif
+
+# Parse and write the JSON response to a file
+parseo parse ST_20240101T123045_S2_E15N45-03035-010m_V100_PPI.tif --output result.json
+
+# Assemble from the saved JSON document. The CLI automatically
+# extracts the `fields` entry produced by `parseo parse`.
+cat result.json | parseo assemble --family copernicus:clms:hr-vpp:st --fields-json -
+
+# Pipe the parse result directly into assemble
+parseo parse ST_20240101T123045_S2_E15N45-03035-010m_V100_PPI.tif \
+  | parseo assemble --family copernicus:clms:hr-vpp:st
+
+# Assemble the same CLMS filename from key=value pairs
+parseo assemble
+  product=ST
+  timestamp=20240101T123045 
+  sensor=S2
+  tile_id=E15N45
+  epsg_code=03035
+  resolution=010m
+  version=V100
+  variable=PPI
+  extension=tif
+```
+
+### Discover available schemas
+
+List every schema that ships with parsEO, including its fully qualified `schema_id`, semantic version, lifecycle status, and file location:
+
+``` bash
+parseo list-schemas
+```
+
+The command prints a table summarizing all discovered schemas, making it easy to confirm which versions are available before parsing or assembling filenames. The first column shows the complete namespace (for example `copernicus:clms:hrl:vlcc`), so you can see exactly where a product sits inside the Copernicus hierarchy.
+
+List only the schemas that are marked as `current` with the built-in filter (works on every platform):
+
+``` bash
+parseo list-schemas --status current
+```
+
+To inspect a single family in the summary table, provide the short family name explicitly. You can also pass a namespace prefix to see every schema beneath it:
+
+``` bash
+parseo list-schemas --family S2
+parseo list-schemas --family copernicus
+parseo list-schemas --family copernicus:clms:hrl
+```
+
+For the full schema metadata (fields, examples, etc.), use `schema-info`:
+
+``` bash
+parseo schema-info S2
+```
+
+The JSON response includes the schema's semantic version and lifecycle status so
+you can immediately tell which release you are viewing. To inspect an archived
+version, provide the version number explicitly:
+
+``` bash
+parseo schema-info --version 1.0.0 CLC
+```
+
+### Working with specific schema versions
+
+When multiple schema versions are present, parsEO chooses the one whose `status` is `"current"`. If none are marked current, the highest `schema_version` wins. You can inspect historical schemas with `parseo schema-info --version <x.y.z> <family>` and you can always pin a schema by passing `schema_path` to `assemble` or `parse`.
+
+## Authoring new Schema
+
+Adding a schema requires only a JSON document under `src/parseo/schemas/`. Start from an existing product schema or the skeleton in `template/`.
+
+-   **Create the product directory** – `src/parseo/schemas/<family>/<mission>/<product>/` (only the family level is mandatory).
+
+-   **Write the versioned schema file** – `<product>_filename_vX_Y_Z.json` with required metadata (`schema_id`, `schema_version`, `status`, optional `stac_version`, `stac_extensions`, and `description`).
+
+-   **Maintain versions** — mark the latest schema as `"current"` and move older ones to `"deprecated"` (or similar). parsEO uses these flags to pick defaults.
+
+    **Schema versioning policy:** Schemas at version `0.0.0` are provisional — their patterns and field definitions may change without notice. Once a product's naming convention is finalised (typically when it reaches CDSE production), the schema should be promoted to `1.0.0` to signal a stable, supported contract.
+
+### Container Object `fields`
+
+**`fields`** is a container object to define filename tokens and translation mechanisms from/to STAC. Each `property` combines JSON Schema keywords (`type`, `pattern`, `enum`, …) and optional documentation. The `property name` is the variable name used by the `template` container and unless a `stac_map` is applied also what is retrieved by `parseo parse` or fed into `parseo assemble`.
+
+``` json
+"fields": { 
+  "property-1": {
+    "type": "string", 
+    "enum": ["A","B"], 
+    "description": "descripton of property 1"
+  },
+  "property-2": {
+    "type": "string", 
+    "pattern": "^(\d{8}T\d{6})$", 
+    "description": "descripton of property 2"
+  },
+  ...
+}
+```
+
+#### `type`
+
+The keyword `type` is currently set to "string" by default, and used as best practice.
+
+#### `enum` or `pattern`
+
+-   Use `enum` for short, controlled vocabularies such as file extensions or processing modes (`["A","B"]`). It keeps validation strict and self-documenting.
+-   Use `pattern` for structured tokens like timestamps (`^\d{8}T\d{6}$`), version identifiers (`^V\d{3}$`), or grid identifiers (`^h\d{2}v\d{2}$`).
+
+#### `oneOf`
+
+Use `oneOf` to express mutually exclusive validation branches for a single field. Each branch can provide its own JSON Schema keywords, enabling concise modelling of tokens that admit multiple formats. For example, a `variant` token may allow either a fixed set of legacy values or a future-proof pattern:
+
+``` json
+"variant": {
+  "type": "string",
+  "oneOf": [
+    {"enum": ["A", "B", "C"]},
+    {"pattern": "^X\d{2}$"},
+    {"pattern": "^z\d{4}$"}
+  ],
+  "description": "Legacy letters or experimental codes"
+}
+```
+
+When `parseo parse` runs, the value is checked against each branch in order until one succeeds. `parseo assemble` accepts any value satisfying at least one branch, allowing schemas to stay expressive without duplicating fields.
+
+#### `stac_map`
+
+Functionality to connect filename tokens to STAC properties in case of incompatibility. In the following example `parseo parse` matches the filename field `prefix` but returns the STAC compliant `platform` and `instrument`. `parseo assemble` must be provided with `platform` and `instrument` and converts it to the correct `prefix` as defined by the filename `template`.
+
+``` json
+"prefix": {
+  "type": "string",
+  "pattern": "^(MOD|MYD|MCD)$",
+  "stac_map": {
+    "MOD": {
+      "platform": "Terra", 
+      "instrument": "MODIS"
+    },
+    "MYD": {
+      "platform": "Aqua", 
+      "instrument": "MODIS"
+    },
+    "MCD": {
+      "platform": "Combined", 
+      "instrument": "MODIS"
+    }
+  }
+}
+```
+
+
+#### Container Object `template`
+A filename is assembled/parsed based on the definition put into `template` container object. E.g.:
+
+``` json
+"template": "{variable}-C{reference_year}_R{resolution}_{tile_id}{epsg_code}_{version}[.{extension}]"
+```
+
+`fields` are added to the `template` using the `{property name}`. The template further decides for the fields are arranged and how they are separated from each other. Further it is possible to ad permanent elements as well, e.g. adding a prefix `C` to the `{reference_year} = C{reference_year}` to match e.g. 'C2012'. This can be particularly useful if you are interested in only parts of the field, e.g. by doping `EPSG{epsg_code}` you fetch only the code itself. This can also be a regex, e.g. `..._(S|C){reference_year}_...`.
+
+Optional filenames must be encapsulated in `[]`. E.g. `[.{extension}]`
+
+#### Container Object `examples` 
+
+Populate `"examples"` with valid filenames covering typical combinations of optional tokens. Test routines will run the examples to assess the proper functioning.
+
+### Test round-trips
+
+run `parseo parse <filename>` and `parseo assemble --schema <schema_path>` to confirm the schema behaves as expected.
+
+### Run unit tests
+
+Install the pytest python package.
+
+from the top-level directory, run `pytest` to launch all tests, or e.g `pytest tests/test_schema_examples_round_trip.py`
+
+### Run as API
+
+parsEO functions can be exposed through a web service. The example below uses [FastAPI](https://fastapi.tiangolo.com), which provides an automatic Swagger UI for trying out the endpoints.
+
+``` python
+# Safe to file: main.py
+from fastapi import FastAPI
+from parseo import assemble, parse_auto
+
+app = FastAPI()
+
+@app.get("/parse")
+def parse_endpoint(name: str):
+    res = parse_auto(name)
+    return res
+
+@app.post("/assemble")
+def assemble_endpoint(schema: str, fields: dict):
+    filename = assemble(fields, schema_path=schema)
+    return {"filename": filename}
+```
+
+Install fastapi and uvicorn (in a python virtual environment):
+
+``` bash
+python3 -m venv .venv
+source .venv/bin/activate
+```
+
+Install the required dependencies (fastapi and uvicorn):
+
+``` bash
+(.venv) pip install fastapi uvicorn[standard]
+```
+
+from the console inside the same directory start the app:
+
+``` bash
+(.venv) python -m uvicorn main:app --reload
+```
+
+Open <http://127.0.0.1:8000/docs> to access Swagger UI:
+
+The interactive page lets you call `/parse` and `/assemble` directly from the browser to verify the API.
+
+
+## Contributing
+
+-   Place new schemas under `src/parseo/schemas/<product_family>/`.
+-   Include at least one positive example in each schema file.
+-   Run the test-suite with `pytest` (and `ruff check .` for linting) before opening a pull request.
+-   Submit a pull request describing the new products or fixes.
+
+## License
+
+This project is licensed under the [European Union Public Licence v1.2](LICENSE.txt).

parseo-0.4.4.dist-info/RECORD

@@ -0,0 +1,70 @@
+parseo/__init__.py,sha256=opqEAAFoBmJEhJxgbab41_V0GVMeu1A3RMya6jFHJQA,1414
+parseo/_epsg_lookup.py,sha256=2x5iWe362V18-9yvs1ZMmrpNTXFtHUinPYFWh36m6SQ,3519
+parseo/_field_mappings.py,sha256=aL921FsdmwedkZtKR44Di1f6YtRsdw6s31gvgRKIEJQ,6899
+parseo/_json.py,sha256=jsooZYiYg3DTte971JuBgUWehJwxmq-LA6CvG5Dft9I,353
+parseo/_tile_systems.py,sha256=nuE-TPMBrKXE60cwHoNWHasM2fc_mc1n5zrFpiTV5Xw,1134
+parseo/assembler.py,sha256=c45_0JkSQjfEA3GKq_TeEMDwdEkdlXvyvk0H_I6r2L4,7396
+parseo/cli.py,sha256=2hhbQnD76v5yTyaJ9_zrOoqKa_J7gyoxK6FigEEUGk4,13228
+parseo/parser.py,sha256=H_E-k-QO49oX70A5m0NIJlEKFzOPTxd2DSAYPvqDLlE,26377
+parseo/schema_registry.py,sha256=m9QG8kOvwnSuVsrrBFxJRNOM2BjkjyWWixj4nVBLE2A,7434
+parseo/stac_http.py,sha256=XNIrA1MKBfY3f_YbtWRqfdn8P1Nk5d5A3AwpqiGtH9o,10086
+parseo/stac_scraper.py,sha256=Tn-YxBPcsQwieU6VeEvroLRp8stQXT0TX0onC64C6A4,4130
+parseo/template.py,sha256=5D01EIwyvZk4OnWtV5iPiKWA4BCeoIuC1yMnb8nC5R4,2588
+parseo/schemas/copernicus/clms/clc/clc_filename_v1_0_0.json,sha256=Wx1E7V6sG-0R4QCBi8dUBs4DRKudMIMvMT5-rgEKtuM,1273
+parseo/schemas/copernicus/clms/clc/clc_filename_v1_1_0.json,sha256=3WiWVch82ecdljEwlVAt7-a7EGo4H4Xfu-HoL66EB2A,2037
+parseo/schemas/copernicus/clms/clcplus/ras/clcplus_filename_v0_0_0.json,sha256=QcymUmO-RHKEFyaHJlitNseDYB9ZHID3hiuda74fINw,2541
+parseo/schemas/copernicus/clms/clcplus/ras/clcplus_filename_v0_0_1.json,sha256=s82NXdbbuaY7qPUA0DG-IagTN6-i3ce87k2DqjfxW88,2139
+parseo/schemas/copernicus/clms/egms/egms_gnss_model_filename_v0_0_0.json,sha256=ujNKUCflE1gcSIR8mglaKdQTb-0cHmgYYwIXVtyEhV0,1115
+parseo/schemas/copernicus/clms/egms/egms_l2a_product_filename_v0_0_0.json,sha256=LOj-EksLnJ7sLTJJJPnUMKHJCqn6JxLq_j1HFoL97xs,1988
+parseo/schemas/copernicus/clms/egms/egms_l3_velocity_grid_filename_v0_0_0.json,sha256=DRHAcDS1UwW6-_MD2bMbFzzFLkU1-GTX40wU-L6LYPk,1761
+parseo/schemas/copernicus/clms/euhydro/euhydro_filename_v0_0_0.json,sha256=3kfZaa9pZD-IDcHimKqyg8ptWcmWOLTHBHZp83OJdGw,3346
+parseo/schemas/copernicus/clms/euhydro/euhydro_filename_v0_0_1.json,sha256=nobaYHLlQWF1tZR44GViKNn4ZF7ud3L2SNq6WDLrQm4,2744
+parseo/schemas/copernicus/clms/hr-vpp/st_filename_v0_0_0.json,sha256=kjTBUsAjOkSzthGPQiclHWDGqBY-qLBZuCTSBFxLOCQ,2336
+parseo/schemas/copernicus/clms/hr-vpp/vi_filename_v0_0_0.json,sha256=n8XfkmmlYQE1-9rZ2ZizSgFPPHjwH-UuQ2LX01bq9Wk,2357
+parseo/schemas/copernicus/clms/hr-vpp/vpp_filename_v0_0_0.json,sha256=KXFv16cnn6y4LM7-H-eKmzPhQkom1GW1_ENvlPMreL8,2944
+parseo/schemas/copernicus/clms/hr-wsi/cc_filename_v0_0_0.json,sha256=iyIhJGHmGN4h-83h9SfyGXQ2CR5cp9m9I_dHdiD6w7I,1950
+parseo/schemas/copernicus/clms/hr-wsi/fsc_filename_v0_0_0.json,sha256=0GqCGw--v3cE1CjoN8cxTsw1RtwQwIDqzMsMDzV-Mqk,2042
+parseo/schemas/copernicus/clms/hr-wsi/gfsc_filename_v0_0_0.json,sha256=i-UbTKBs0rEYZyaZIl1ORieveWKNWA-EOrP7xOglQ7s,1936
+parseo/schemas/copernicus/clms/hr-wsi/icd_filename_v0_0_0.json,sha256=xDeNbL1OHzz68kJa8NpsbsQrOVLQO0VA7b2reDBd7ms,2389
+parseo/schemas/copernicus/clms/hr-wsi/sp_filename_v0_0_0.json,sha256=XnyC6JI4U2iEWZQnTyCu4j6EYimVbhNRkq2Av6v8Ctk,3824
+parseo/schemas/copernicus/clms/hr-wsi/sws_filename_v0_0_0.json,sha256=_2qzZt-psb5ebVULllmM6lsSYenyyetTv3bbD-my43I,1945
+parseo/schemas/copernicus/clms/hr-wsi/wcd_filename_v0_0_0.json,sha256=jdHLFmv_XZVmWKO2hkSvDvO5yRqqS7F0ty28RXGu73s,2445
+parseo/schemas/copernicus/clms/hr-wsi/wds_filename_v0_0_0.json,sha256=Sogqu4pK2XHsq6aC3uIfMbV13gP_Rz5DK6cDD_M6RVk,1966
+parseo/schemas/copernicus/clms/hr-wsi/wic_comb_filename_v0_0_0.json,sha256=zqnJdTWbNzbREucSIXI9jwI16tqLaMHcsxtb2IBsetg,1959
+parseo/schemas/copernicus/clms/hr-wsi/wic_filename_v0_0_0.json,sha256=pGIqjEZnnC9rBV_KjlahE4ZBybobF3sbAWi1a_hLhPk,2134
+parseo/schemas/copernicus/clms/hrl/fty_filename_v0_0_0.json,sha256=mTaX9mL1vSnPuqTa6hg6UDzjvbQ7vNgQjWF0c--osm8,1299
+parseo/schemas/copernicus/clms/hrl/gra_filename_v0_0_0.json,sha256=PCYQMwSAU2UQY05RXp1DMEDB5ga4xs6Axw244n5yOZg,1295
+parseo/schemas/copernicus/clms/hrl/ibu_filename_v0_0_0.json,sha256=JD04nSYB4Si4By4IXbknvfTh_raEARXsvL4YPTQATjA,1644
+parseo/schemas/copernicus/clms/hrl/imp_filename_v0_0_0.json,sha256=oH2SVF1Kv7_lKOQmf-JdAVV7IQ65_f4IDTr9XmalKvw,1294
+parseo/schemas/copernicus/clms/hrl/nvlcc_filename_v0_0_0.json,sha256=kcKPmjJA4Vs4YRKmCqMGhSEkzHPU5hrAUcdHp0JZSp4,2290
+parseo/schemas/copernicus/clms/hrl/nvlcc_filename_v0_0_1.json,sha256=O9Y5i2kqMISkgVS3nhaOmlCazW2ygcvwgoyYEVq-Z38,2839
+parseo/schemas/copernicus/clms/hrl/nvlcc_filename_v0_0_2.json,sha256=JdGPDIJ8YDLifhHJYYSXn5jw_KKt6741mHBMQoJFQl4,2833
+parseo/schemas/copernicus/clms/hrl/swf_filename_v0_0_0.json,sha256=FRnwSvfPQSt5DLT_Z50eQ-v-nEDie8Xnu8zz47n_w_g,1303
+parseo/schemas/copernicus/clms/hrl/swf_filename_v0_0_1.json,sha256=jkoHU1n46aXKGOgVmgRnj7-k2C2kvjcT57Zj2JZJb84,1361
+parseo/schemas/copernicus/clms/hrl/swf_filename_v0_0_2.json,sha256=5GpHfvTbr-dceFZi2tbIba9WBatUpTzYYKQCv7yW6iI,3054
+parseo/schemas/copernicus/clms/hrl/swf_filename_v0_0_3.json,sha256=O3w1EUb-o7AR5473ra_0tlgwEw8X71fNK9LJnS6UuuY,3327
+parseo/schemas/copernicus/clms/hrl/tcd_filename_v0_0_0.json,sha256=Mfu9qcOOuyo6BVNN4XoY7bhXo0xWJiPTzszWog81Mrk,1298
+parseo/schemas/copernicus/clms/hrl/vlcc_filename_v0_0_0.json,sha256=BywmPoNQcokP2aIQm6ifCZ_Fxn7nPcBD_QrWGBZ7kvo,3796
+parseo/schemas/copernicus/clms/hrl/waw_filename_v0_0_0.json,sha256=W0FFsTE7d1MgPnXQox807-VqvoVWPcKsNNi0YOPy-6c,1295
+parseo/schemas/copernicus/clms/n2k/n2k_filename_v1_0_0.json,sha256=T2to8-0jV-NAB4HwZdtbsZgEIKsoS47LWXE9J-9ZG3o,1146
+parseo/schemas/copernicus/clms/pa/pa_filename_v1_0_0.json,sha256=fpJjEkDlKa-LaIKFcagKr4ELpZALsR97_VQkhpFcWGk,2728
+parseo/schemas/copernicus/clms/riparian-zones/rpz_filename_v0_0_0.json,sha256=gOnLwQb8YIfSOKnNBVn0I2QZaMX2Z-vLr0R8NVZd_B0,1271
+parseo/schemas/copernicus/clms/urban-atlas/ua_dhm_filename_v0_0_0.json,sha256=qoOwRTAurcN4tTxHPiR8X_PS00NzQrvxDA6s3P5W44E,1456
+parseo/schemas/copernicus/clms/urban-atlas/ua_filename_v0_0_0.json,sha256=CeeJ5F15r4450OVwQ5U1U3BL1Fqhxm1aeATVpr6bZEg,3083
+parseo/schemas/copernicus/clms/urban-atlas/ua_stl_filename_v0_0_0.json,sha256=74tKrcVhM3DvFKBvGrs5fWVLhqhQgvSH8vlNGgE0668,2485
+parseo/schemas/copernicus/sentinel/s1_filename_v1_0_0.json,sha256=B05ONYUgPJXWf22A94nwO9Sedrna_KfNiS6J6FkFJZk,2676
+parseo/schemas/copernicus/sentinel/s2_filename_v1_0_0.json,sha256=HaZsgJWM61A519SwozvUDNfSWSnQDih20RQy061gyz0,1982
+parseo/schemas/copernicus/sentinel/s3_filename_v1_0_0.json,sha256=pl3Z7RMh8xSBJKBLVy3mtriPxVYKfxHmb7DB__tjxAw,1353
+parseo/schemas/copernicus/sentinel/s4_filename_v1_0_0.json,sha256=HUltPy_dzGpzY-VhI672X7-KbwTsvOACFOnJ5Tprc_c,902
+parseo/schemas/copernicus/sentinel/s5p_filename_v1_0_0.json,sha256=tymR-OaPA1M8XJ269NRDo6qBUZBr7YqxrxeN5F2nYPg,924
+parseo/schemas/copernicus/sentinel/s6_filename_v1_0_0.json,sha256=Zos88LqbeUwE4WD4Lmh0O7v5qpcNXP7xx7P8qc86ATg,1075
+parseo/schemas/eumetsat/metop_filename_v1_0_0.json,sha256=D9na0QufeUI8BtqBdNY7p6mvWA8Qle8AmhBCmhrHdS8,1689
+parseo/schemas/eumetsat/mtg_filename_v1_0_0.json,sha256=xCcdYQXyOlYMUG6O5KulqddUj-Jb3xT7h5a2baQaDiU,1596
+parseo/schemas/nasa/modis_filename_v1_0_0.json,sha256=mlS0PHaEX8IZYAOmXO-JIbDP5tQ-P7XCP-lXeV4ZIYo,1921
+parseo/schemas/usgs/landsat/landsat_filename_v1_0_0.json,sha256=Hjh_PrnyNUX4hmFT9vSDFtogiTDDHGr-EwStY1OkFZs,1986
+parseo-0.4.4.dist-info/licenses/LICENSE.txt,sha256=b8nnCcy_4Nd_v_okJ6mDKCvi64jkexzbSfIag7TR5mU,13827
+parseo-0.4.4.dist-info/METADATA,sha256=VbRbzoczGk4f-2a-ngGh1oWMn-md28RwOk0KwCFfTi4,15097
+parseo-0.4.4.dist-info/WHEEL,sha256=YVMoNqKzERt-wjUZwJ33xBGAwnFl-4cqbYkTtWa4itE,91
+parseo-0.4.4.dist-info/entry_points.txt,sha256=dFGisbioM3P8UeYD0WYQYrNcxdc4RSsCMb7N2PgdLXE,43
+parseo-0.4.4.dist-info/top_level.txt,sha256=yxQJTOitKnP3h7Ji6r0G0SuCcJIRGzsr4qu0VCWBrXA,7
+parseo-0.4.4.dist-info/RECORD,,

parseo-0.4.4.dist-info/WHEEL

@@ -0,0 +1,5 @@
+Wheel-Version: 1.0
+Generator: setuptools (84.0.0)
+Root-Is-Purelib: true
+Tag: py3-none-any
+

parseo-0.4.4.dist-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+parseo = parseo.cli:main