Clarify GeoJSONL spec

Open
#50 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
documentation

Research direction

Read the current GeoJSONL documentation and compare it with the line-by-line GeoJSON article linked in the issue. Review the linked Slack discussion for context on how this project's format differs from other uses. Done means the MapRoulette GeoJSONL specification clearly states its own rules and resolves any identified ambiguities.

Written by the indexing model from the issue text.

Description

Our spec is different from the various "specs" that live out there on the internet. Note that there is no official GeoJSONL spec, but that's all the more reason we should be clear about ours.

See https://osmus.slack.com/archives/C04M1NHPEQY/p1740551156419729

I think https://learn.maproulette.org/en-us/documentation/line-by-line-geojson/#content is pretty clear but if there is room for improvement we should consider it.

Dominant language
SCSS
Stars
5
Forks
8
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 maproulette/docs

All issues in maproulette/docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.