需要 CMake 版本满足 3.21 ≤ cmake < 3.25（OpenSceneGraph 3.6.x 在 cmake ≥ 3.25
下构建失败，实测踩坑）。pyproject.toml 的 build-system 已固定 cmake==3.24.3
（构建隔离环境自动安装，无需改动机器上的系统 cmake）。
构建脚本
chcp 65001 && uv build --wheel --out-dir dist
cython 测试
python -m cython --cplus -3 --fast-fail -I "src/alosg" -o "test_manual.cxx" "src/alosg/alosg.pyx"
创建入口代理节点
import alosg
# # 仅分析，返回根瓦片绝对路径列表
# roots = alosg.find_osgb_roots(r"D:\数据\倾斜模型")
# 全量扫描（原行为）
roots = alosg.find_osgb_roots(r"D:\模型")
# Bentley / iTwin 类数据
roots = alosg.find_osgb_roots(r"D:\模型", mode="bentley", sub_path="Data")
# 大疆智图
roots = alosg.find_osgb_roots(r"D:\模型", mode="dji")
# 生成入口
ok, roots = alosg.create_preview_entry(
r"D:\模型",
r"D:\模型\preview_entry.osgb",
mode="dji",
)
1 maintainer
Metadata
1 maintainer
Release files for alosg 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| alosg-0.2.1-cp314-cp314-win_amd64.whl | CPython 3.14 | CPython 3.14 | Windows x86-64 | Details for alosg-0.2.1-cp314-cp314-win_amd64.whl |
| alosg-0.2.1-cp313-cp313-win_amd64.whl | CPython 3.13 | CPython 3.13 | Windows x86-64 | Details for alosg-0.2.1-cp313-cp313-win_amd64.whl |
| alosg-0.2.1-cp312-cp312-win_amd64.whl | CPython 3.12 | CPython 3.12 | Windows x86-64 | Details for alosg-0.2.1-cp312-cp312-win_amd64.whl |
| alosg-0.2.1-cp311-cp311-win_amd64.whl | CPython 3.11 | CPython 3.11 | Windows x86-64 | Details for alosg-0.2.1-cp311-cp311-win_amd64.whl |
Total release size: 12.5 MB
Release files / alosg-0.2.1-cp314-cp314-win_amd64.whl
| Download URL | alosg-0.2.1-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 3.2 MB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
835076b299d84492aafe0d94dd1f27816414e57b0991a87e8155ece2fa9cecd7
|
|
BLAKE2b-256 checksum How to use checksums |
36ec329cc38d38918ba3085ef5749cc54319c4dde46be5c24e47e146b5a62a1e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Release files / alosg-0.2.1-cp313-cp313-win_amd64.whl
| Download URL | alosg-0.2.1-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 3.1 MB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
0f0177e75fbad7fe9ca37354d3461005dfeb28fd791408c1e4c9be087a151915
|
|
BLAKE2b-256 checksum How to use checksums |
2beb2ecf45f63618007b5c69fe0d3d326b03eeec8a940e6bec27a50a2b9a6e4c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Release files / alosg-0.2.1-cp312-cp312-win_amd64.whl
| Download URL | alosg-0.2.1-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 3.1 MB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
3187d7020e2c058f591735aa67f5a2f0b83ee75fd48a4e72cd79465f77162bd2
|
|
BLAKE2b-256 checksum How to use checksums |
ec74dff3614f377757c2e22c8618a215ad8490d9425d58af4b4af5ae166decc4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Release files / alosg-0.2.1-cp311-cp311-win_amd64.whl
| Download URL | alosg-0.2.1-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 3.0 MB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
7bf619c5a386d0751ec010b59b9fff4ec927be75ad47a8a6f364965bce5af214
|
|
BLAKE2b-256 checksum How to use checksums |
4c56dc05dca638230aee614447e5bdca36316b2bb1f700139d2519486c3b2b41
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Security for alosg 0.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
