WKID question of OGCGeometry.fromText() and OGCGeometry.fromBinary()
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
Start with OGCGeometry.fromText(String) and the corresponding fromBinary method, then compare their spatial-reference handling with fromGeoJson and fromJson. Investigate how relation methods such as st_contains and st_intersects use spatial references. Done means establishing and documenting the expected WKID behavior for non-4326 inputs.
Written by the indexing model from the issue text.
Description
public static OGCGeometry fromText(String text) {
OperatorImportFromWkt op = (OperatorImportFromWkt)OperatorFactoryLocal.getInstance().getOperator(Type.ImportFromWkt);
OGCStructure ogcStructure = op.executeOGC(0, text, (ProgressTracker)null);
return createFromOGCStructure(ogcStructure, SpatialReference.create(4326));
}
For this function (same as fromBinary), it will output OGCGeometry using the WKID 4326 directly. If the input text has some information of SRID which is not 4326, what should we do? Or current api for all the relations (such as st_contains, st_intersects etc.) is just suited for 4326 spatial reference system. In the function fromGeoJson or fromJson, it will parse the WKID from the Json input and set the SpatialReference. Here, I have a question: if the SRID is not 4326, when we do the relation query for these geometries, do we use the spatial reference system in the input JSON, or we change the spatial reference system to the 4326? Thank you!
- Dominant language
- Java
- Stars
- 710
- Forks
- 268
- Avg merge
- 7d 23h
- Merged PRs (30d)
- 1
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.
More from Esri/geometry-api-java
-
bug fixed_to_verify
Esri/geometry-api-java#328 · 3 comments · 1 assignee ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Esri/geometry-api-java#324 · 17 comments · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Esri/geometry-api-java#321 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
Esri/geometry-api-java#320 · 1 comment ·
-
cannot reproduce
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Esri/geometry-api-java#316 · 5 comments ·
All issues in Esri/geometry-api-java
Similar issues
-
certification
Difficulty 1/5 Under an hour Newbie friendliness 80/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
[BUG] ECR GetAuthorizationToken returns a proxyEndpoint for the default region, not the request's Openbug ecr
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Needs: Triage Type: Feature request
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
AntennaPod/AntennaPod#8794 ·
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
github/copilot-sdk#2760 ·