Correcting an error on openstreetmap (badly formed multipolygon)
ฝัง
- เผยแพร่เมื่อ 28 ก.ย. 2024
- This is not a tutorial on JOSM (there are many good ones online),
but just a live example of correction that could be helpful to some
of the Ortho4XP users.
It doesn't open in JOSM...
I do an edition by ID Editor. Ortho4xp reads all update of OSM website?
Hallo Oscar
My mistake I've done something wrong, I have them all now. and they look beautiful in ZL 18
I still have a question, I made tiles from Bali (Indonesia) with BI, and it looks terrible.
Which source do you advice for example Indonesia, Hongkong China area, Himalaya, Nepal, Buthan, India.
For Indonesia Bali, i dit look first to the preview, in ZL 13, ARC was the best, but when i made the tiles in ZL 18 there ware only white faces that ware downloaded. Gladly your advice?
Thank you for your lovely program Ortho4XP for Windows.exe
Regards
Peter
Hallo Peter,
Indeed imagery sets usually differ at high and low zoomlevels. For regions with poor coverage the only
two solutions are 1) patience it will improve some day 2) low ZL like Arc 13 as you mentioned.
Regards
Hallo Oscar
Irecently started using Ortho4XP, the Windows.exe version, and have already downloaded some very beautiful Tiles of England, Belgium and parts of the nederlands, because I ame Dutch I would like to have all of the nederlands.
But if I want to download +52+4 the osm data has so many errors that it fails.
As I look at the osm data errors I see Relation id=1155066 is ill formed and was not treated.
Relation id=1386139 contains a member with role different from inner or outer, it was not treated. in total 45 like this.
The area +52+4 is very large, and the id numbers of the errors give me no clue where I can find this error on the openstreet map to correct them.
Can you give me a clue how to start? regards Peter
It works here. It lists some errors but this is very common and most are harmless, you'd just need to look at them if you notice something wrong in the sim. With default settings I get 800k edges at step 1 and 1.5M tri at Step2. More stressful settings work as well. Try to purge OSM your data just in case.