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
Describe the bug
OSM has a limit of 2,000 nodes per way. Many linear features with which our project deals have more than 2,000 vertices and when such features are exported they should not be split. One method of addressing this limitation is to introduce a new relation type=multilinestring which would be similar to type=multipolygon.
To Reproduce
Import/upload linear feature with more than 2,000 vertices
Export above data (e.g. to a shapefile)
Expected behavior Import
linestrings/polylines are broken into ways of 2,000 nodes or less.
A relation is created with type=multilinestring
Above ways are added to above relation
Tags from the original feature are added to the relation
Ways receive no tags
Export
Relations with type=multilinestring become a single linestring/multilinestring/polyline in the output
Tags (other than type=multilinestring) from the relation are turned into the corresponding field values on the above linestring
Translations via API
Relation type=multilinestring should be treated as a linear feature
Screenshots
N/A
Desktop (please complete the following information):
N/A
Smartphone (please complete the following information):
N/A
Additional context
None
The text was updated successfully, but these errors were encountered:
Describe the bug
OSM has a limit of 2,000 nodes per way. Many linear features with which our project deals have more than 2,000 vertices and when such features are exported they should not be split. One method of addressing this limitation is to introduce a new relation type=multilinestring which would be similar to type=multipolygon.
To Reproduce
Expected behavior
Import
Export
Translations via API
Screenshots
N/A
Desktop (please complete the following information):
N/A
Smartphone (please complete the following information):
N/A
Additional context
None
The text was updated successfully, but these errors were encountered: