You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The geometry filter "other" is not well defined (at least not in the docu of the ohsome-api). It remains unclear what it contains, apart from geometry-collections.
Expected Solution
Be explicit on the filters. Add filters for Polygon vs MultiPolygon (vs Polygonal) etc.
Alternative Solutions
Document what 'other'-geometry type is.
### Additional Context Add any other context or screenshots about the feature request here.
Yes, the documentation is concise, but IMHO sufficient: ”matches anything which has a geometry of the given type (point, line, polygon, or other)” means that other is everything that is not a point, line or polygon.
Polygon vs MultiPolygon (vs Polygonal)
geometry:polygon is implemented to match everything that is polygonal. I used the simpler wording on purpose in the docs, as it is more easily understandable. Also, I think it's not necessary to provide more detailed filters for only MultiPolygon or non-multi polygonal geometries.
/** A polygon or multipolygon geometry (JTS: {@link Polygonal}). */
POLYGON,
/** A geometry collection which is not a multipolygon. */
OTHER
}
because it links to Puntual/Lineal but only considers Points/Lines. MultiPoint or MultiLinestrings are considered GeometryType.OTHER (if they are even recognised?).
I'm sorry for being such a nit-picker but downstream tools require me to be exact on my geometries.
Problem Description
The geometry filter "other" is not well defined (at least not in the docu of the ohsome-api). It remains unclear what it contains, apart from geometry-collections.
Expected Solution
Be explicit on the filters. Add filters for Polygon vs MultiPolygon (vs Polygonal) etc.
Alternative Solutions
Document what 'other'-geometry type is.
### Additional ContextAdd any other context or screenshots about the feature request here.Related: #436
The text was updated successfully, but these errors were encountered: