[Bug] g.proj: projjson output fails with PROJ 9.8.1

Open
#8,085 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
c
Domain
backend

Research direction

Start at the g.proj code path that produces PROJJSON and inspect how it builds the input passed to PROJ. Reproduce with g.proj -p format=projjson on nc_spm_full_v2alpha2 using PROJ 9.8.1, then compare with a projection that succeeds. Done means the affected projection prints valid PROJJSON without the conversion warning.

Written by the indexing model from the issue text.

Description

bug

Describe the bug

Printing the projection in projjson format for nc_spm_full_v2alpha2 fails with

> g.proj -p format=projjson                            Mapset <user1> in <nc_spm_full_v2alpha2>
proj_create_from_wkt: missing required input
WARNING: Unable to convert to PROJJSON

I suspect this is caused by the newer PROJ version, but I haven't (been able to) double checked.

System description

This is tested on main but also reproducable with 8.5.

> g.version -rge                                                                                                                         Mapset <user1> in <nc_spm_full_v2alpha2>
version=8.6.0dev
date=2026
revision=ab1d24f661
build_date=2026-10-19
build_platform=aarch64-apple-darwin25.6.0
build_off_t_size=8
libgis_revision=a92cbed035
libgis_date=2026-10-17T05:24:42+00:00
proj=9.8.1
gdal=3.13.3
geos=3.15.0
sqlite=3.53.4

Additional context

This is not an issue on all projects/projections, nc_spm_full_v2alpha2 is the only one I noticed so far.

Dominant language
C
Stars
1.2k
Forks
447
Avg merge
1d 19h
Merged PRs (30d)
62

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OSGeo/grass

All issues in OSGeo/grass

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.