update doc

[satoshi7190]

Close #0

What I did（変更内容）

• ORDER_MAPにxALのキーを追加
• ドキュメントの更新

Notes（連絡事項）

• docs/src/make_mapping_rule_doc.shのinputファイル名の先頭に.が入っていいて、スクリプトが動かなかったので削除しました（何か意図があれば戻します）

[coderabbitai]

Walkthrough

このプルリクエストは、ドキュメント生成スクリプトに2つの小さな変更を加えています。1つ目は make_mapping_rule_doc.sh スクリプトで、ファイル名からリーディングドットを削除しています。2つ目は schema_to_doc.py で、ORDER_MAP に新しいエントリを追加し、出力フォーマットを微調整しています。これらの変更は主にドキュメント生成プロセスの細かい調整に焦点を当てています。

Changes

ファイル	変更の概要
docs/src/make_mapping_rule_doc.sh	ファイル名から先頭のドットを削除 (.64413325_bldg_6697_op.gml → 64413325_bldg_6697_op.gml)
docs/src/schema_to_doc.py	ORDER_MAP に "xAL": 15 を追加、出力フォーマットの微調整

Possibly related PRs

• PLATEAU V4に対応 #691: PLATEAU V4の互換性に関連するデータ構造の処理変更

Suggested reviewers

• nokonoko1203

Poem

🐰 コードの旅路、一歩ずつ
ドットを消し、型を並べ
ドキュメントは輝く宝石
静かに変わる、スクリプトの詩
コンパイラは微笑む 🌟

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

docs/src/make_mapping_rule_doc.sh (1)

3-3: シェルスクリプトの堅牢性を改善する機会

ファイル名から不要なドットを削除したのは適切な変更です。しかし、以下の改善を推奨します：

+#!/bin/bash
+set -eu
+
 for FILE_FORMART in shapefile gpkg geojson czml kml mvt 3dtiles
 do
     cargo run -p nusamai -- 64413325_bldg_6697_op.gml --schema schema_${FILE_FORMART}.json --sink $FILE_FORMART --output out.dummy
+    if [ $? -ne 0 ]; then
+        echo "Error processing ${FILE_FORMART}"
+        exit 1
+    fi
 done

変更点の説明：

1. シェバン行の追加でスクリプトの実行環境を明示
2. set -euでエラー時の即時終了とunset変数の使用防止
3. エラーハンドリングの追加でトラブルシューティングを容易に

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a8098f2 and dfb63ff.

⛔ Files ignored due to path filters (7)

• docs/src/schema_3dtiles.json is excluded by !**/*.json
• docs/src/schema_czml.json is excluded by !**/*.json
• docs/src/schema_geojson.json is excluded by !**/*.json
• docs/src/schema_gpkg.json is excluded by !**/*.json
• docs/src/schema_kml.json is excluded by !**/*.json
• docs/src/schema_mvt.json is excluded by !**/*.json
• docs/src/schema_shapefile.json is excluded by !**/*.json

📒 Files selected for processing (2)

• docs/src/make_mapping_rule_doc.sh (1 hunks)
• docs/src/schema_to_doc.py (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: test
• GitHub Check: build
• GitHub Check: Analyze (javascript-typescript)

🔇 Additional comments (2)

docs/src/schema_to_doc.py (2)

33-33: ORDER_MAPに新しいエントリを追加

xALのエントリ追加は適切で、既存の順序付けパターンと一致しています。

---

87-87: 出力フォーマットの一貫性を改善

スペース調整により、出力テーブルのフォーマットがより一貫性のあるものになりました。

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Additional details and impacted files

Components	Coverage Δ
GUI	∅ <ø> (∅)
Backend	74.64% <ø> (ø)
Libraries	85.87% <ø> (ø)

📢 Thoughts on this report? Let us know!