fixmyberlin/tilda-geo · Archived

create-taginfo-project-file

Generate taginfo project JSON files for TILDA topics, extracting OSM tags from processing code.

First seen Jun 18, 2026

Installation

$ npx skills add fixmyberlin/tilda-geo --skill create-taginfo-project-file

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Also in this package

Other skills from fixmyberlin/tilda-geo.

npx skills add fixmyberlin/tilda-geo

Browse all from fixmyberlin/tilda-geo

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 24
License LICENSE.md
Default branch develop
Open issues 1
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,762 B
  • docs SUMMARY.md 130 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Create Taginfo Project File

Generate valid taginfo project files for TILDA topics by analyzing processing code to extract OSM tags.

When to Use

  • User wants to create taginfo project files for TILDA topics
  • User mentions taginfo, OSM tag documentation, or taginfo project files

Process

  1. Identify topic: Read processing/constants/topics.const.ts or ask user which topic to process
  1. Read topic file: processing/topics/<topic>/<topic>.lua

- SQL files are ignored - they never introduce new tags - **TodoList files (*_todoList.lua) are ignored** - they are for QA purposes and don't represent the main processing logic - Check for README files that may document OSM tags

  1. Extract OSM tags: See references/tag-extraction.md for detailed rules

- Extract only raw OSM tags (before transformations) - Watch for :left, :right, :both variants - extract all used - Infer values from conditional checks and allowed value lists - Exclude tagscc - Tags copied via CopyTags() with tagscc are for data storage only, not filtering/processing logic

  1. Create tag entries: For each tag, determine:

- Whether to include value (specific values only) or omit (all values) - object_types from processing functions (see references/tag-extraction.md) - description focusing on TILDA's use case, not general OSM docs

  1. Generate JSON: Use assets/example.json as template

- Replace <topic> and <timestamp> placeholders - Timestamp format: yyyymmddThhmmssZ (e.g., 20260123T143022Z)

  1. Save file: app/public/taginfo/tilda-<topic>.json (create directory if needed)

Validation

  • JSON validates against taginfo schema (see references/taginfo-schema.md)
  • Required fields present: data_format, project.*, tags
  • Email format valid, URLs valid URIs
  • Object types: "node", "way", "relation", "area" only
  • No wildcards in values, plain text descriptions
  • Only raw OSM tags (no processed/result tags)

References

TILDA Project Info

  • Name: TILDA
  • URL: https://tilda-geo.de/
  • Contact: FixMyCity <[email protected]>
  • Topics: roads_bikelanes, bikeroutes, bicycleParking, trafficSigns, boundaries, places, publicTransport, poiClassification, barriers, landuse, parking