This is an automated email from the ASF dual-hosted git repository.
jiayu pushed a change to branch feature/osm-pbf-metadata-fields
in repository https://gitbox.apache.org/repos/asf/sedona.git
discard dc520de938 [GH-2760] Extend OSM PBF reader to support additional
metadata fields
add 7181135bd4 [CI] Pin astral-sh/setup-uv to ASF-allowed SHA (#2778)
add b1c2ade358 [CI] Pin docker/setup-qemu-action and pypa/cibuildwheel to
ASF-allowed SHAs (#2780)
add f7270acba7 [GH-2760] Extend OSM PBF reader to support additional
metadata fields
add 5ae595e3c0 Address PR review: bounds checks, visible default, and test
assertions
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (dc520de938)
\
N -- N -- N refs/heads/feature/osm-pbf-metadata-fields
(5ae595e3c0)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.github/workflows/docs.yml | 2 +-
.github/workflows/pyflink.yml | 2 +-
.github/workflows/python-extension.yml | 2 +-
.github/workflows/python-wheel.yml | 6 +--
.github/workflows/python.yml | 2 +-
.prettierignore | 2 +
.../osmpbf/extractors/DenseNodeExtractor.java | 46 ++++++++++++++--------
.../datasources/osmpbf/features/InfoResolver.java | 4 ++
.../org/apache/sedona/sql/OsmReaderTest.scala | 22 +++++++++++
9 files changed, 65 insertions(+), 23 deletions(-)
