opengeospatial / opengeospatial/ogcapi-features
Reccomendations/guidelines for axis order?
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 386
- Forks
- 92
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 15
Description
Should the specification give recommendations on axis order, while leaving implementers free to use the axis order they prefer?
Would the order have to be fixed, so that all outputs requested in, say, "http://www.opengis.net/def/crs/EPSG/0/4269" (NAD83), share the same order (ask the same, get the same)?
However, by experience, the "useful" axis order is linked to the chosen output format, shapefiles hardly work in practice when returned in north/east order for example.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the specification’s treatment of the EPSG:4269 CRS and axis order, including the shapefile output example mentioned in the issue. Determine whether the specification should recommend or require a consistent order, and document the decision and its implications for output formats.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100