Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add support for other geometry classes known by WKT #30

Open
navibyte opened this issue May 22, 2021 · 1 comment
Open

Add support for other geometry classes known by WKT #30

navibyte opened this issue May 22, 2021 · 1 comment
Labels
🌎 geodata Related to the code package "geodata" enhancement New feature or request 🌐 geobase Related to the code package "geobase"

Comments

@navibyte
Copy link
Collaborator

https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry

Now (at least some level of) support for:

  • Point, MultiPoint
  • LineString, MultiLineString
  • Polygon, MultiPolygon
  • GeometryCollection

However NO support for these, and not yet even planned any, is there need?

  • Triangle
  • PolyhedralSurface
  • TIN (Triangulated irregular network)

Well-known binary (WKB) seems to have even more, but maybe most of these are totally out of focus for the geocore library...

  • CircularString
  • CompoundCurve
  • CurvePolygon
  • MultiCurve
  • MultiSurface
  • Curve
  • Surface
  • Circle
  • GeodesicString
  • EllipticalCurve
  • NurbsCurve
  • Clothoid
  • SpiralCurve
  • CompoundSurface
  • BrepSolid
  • AffinePlacement
@navibyte navibyte added 🌐 geocore Related to the code package "geocore" 🌎 geodata Related to the code package "geodata" enhancement New feature or request labels May 22, 2021
@navispatial navispatial added 🌐 geobase Related to the code package "geobase" and removed 🌐 geocore Related to the code package "geocore" labels Aug 6, 2022
@navispatial
Copy link
Member

navispatial commented Apr 10, 2024 •
edited
Loading

Better first implement #226 for simple geometries (target on geobase 2.0.0) and then extend support for other geometries too. This issue quite large however, maybe should be splitted (at least those geometries supported by JSON-FG, see #53).

@navispatial navispatial added this to the geobase 3.0.0 milestone Apr 10, 2024
@navispatial navispatial removed this from the v3.0 on dart 3.3 milestone May 26, 2024
@navispatial navispatial mentioned this issue Dec 6, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🌎 geodata Related to the code package "geodata" enhancement New feature or request 🌐 geobase Related to the code package "geobase"
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@navispatial