Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

A column was specified that does not exist

Open
#91 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
data

Research direction

Start by reproducing the post-conversion failure described in issue #91 when opening the attribute table in ArcPro, using the same kind of shapefile output. Compare the exported columns with the fields ArcPro expects, including behavior after removing unique identifier fields. Done means the converted feature still draws and its attribute table opens without the missing-column error.

Written by the indexing model from the issue text.

Description

I'm getting a post conversion error when attempting to open up the attribute table in ArcPro

Could not load data from the data source. If you can correct the problem, press the refresh button to reload data. A column was specified that does not exist

I know this is post conversion but has anybody experienced this? The feature draws and the data associated even displays when you click as a popup in ArcPro. I attempted to remove unique identifier fields from the properties before exporting but the issue still stands.

Dominant language
JavaScript
Stars
321
Forks
193
PR merge metrics
No merged PRs in 30d

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 mapbox/shp-write

All issues in mapbox/shp-write

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.