#10452 closed enhancement (fixed)
When creating new ways with >2,000 points, JOSM does not complain, but upload is impossible
| Reported by: | Andreas_Schmidt | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | 14.09 |
| Component: | Core validator | Version: | tested |
| Keywords: | api capabilities nodes limit | Cc: |
Description
I am creating new very long ways (river in Brasil) with approximately 2,100 waypoints.
Attempt to upload results in error message
"[Anforderungen des API verletzt]
2.089 Punkte in Linie 285966444 überschreitet die maximal erlaubte
Anzahl von 2.000 Punkten."
http://abload.de/img/osm2000c4qgq.png
JOSM somewhat hangs, no Bing image update, undo button (yellow arrow) does not work. So I got stuck.
Later I found out, I can do "Bearbeiten - Rückgängig" (Edit - Undo) in JOSM's menu and deleted my last 89 points, then succeeded in uploading.
I propose, JOSM should complain whenever the number of waypoints reaches 1,999 (or even earlier) instead of accepting edits with >2,000 points, which cannot be uploaded.
Attachments (1)
Change History (12)
by , 10 years ago
| Attachment: | osm2000.png added |
|---|
follow-up: 3 comment:2 by , 10 years ago
In addition some user instructions are nice.
Please split the way. For closed ways use a multipolygon relation.
comment:3 by , 10 years ago
Replying to skyper:
In addition some user instructions are nice.
Please split the way. For closed ways use a multipolygon relation.
agreed.
German translation might be
Bitte teile die Linie auf, dazu kannst du das Tastaturkürzel P nutzen.
comment:4 by , 10 years ago
| Keywords: | api capabilities nodes added; 2 000 points removed |
|---|---|
| Milestone: | → 14.09 |
comment:6 by , 10 years ago
| Component: | Core → Core validator |
|---|---|
| Priority: | minor → normal |
comment:8 by , 10 years ago
Mmh, thanks.
Is a validator warning enough ?
I thought about a direct warning once you exceed the limit.
follow-up: 10 comment:9 by , 10 years ago
It's easier and necessary: validator should detect all cases of data invalidity, that's its job. We'll see later if we add some "real-time" UI feedback but it could be extended to many other editing problems, just not this one.
comment:10 by , 10 years ago
Replying to Don-vip:
It's easier and necessary: validator should detect all cases of data invalidity, that's its job. We'll see later if we add some "real-time" UI feedback but it could be extended to many other editing problems, just not this one.
Yes, validator warning was needed.
Did open #10545 about the "real-time" UI feedback.
screenshot of error message (German language)