Implementation difference between geojson js vs geojson java
Open
Nobody has claimed this yet.
GeoJson
Turf
- Dominant language
- Java
- Stars
- 438
- Forks
- 117
- PR merge metrics
- No merged PRs in 30d
Description
This issue is raised from PR #1075 .
- In the js implementation of
geojson, thepropertiesvalue of aFeaturecan be empty, but in the java implementation, an empty properties field is ignored:
- When converting js version of
geojsonto the java version, the precision of coordinates has been reduced, i.e. from102.227783203125to102.2277832. This issue was introduced in #938 . It seems the precision is trimed due to performance consideration.
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 with Feature.java at the linked properties handling and review PR #1075 and issue #938 for the behavior changes. Compare Java output with the JavaScript GeoJSON behavior for empty properties and coordinate precision; done means both differences are addressed and covered by relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100