2 ms·
> Imports need to be supported. I don't really agree. I have seen so many wrong imports and I have seen imports demotivating individual mappers. With a good d
by johannes1234321 9y ago
> Imports need to be supported.
I don't really agree. I have seen so many wrong imports and I have seen imports demotivating individual mappers.
With a good data source an import can be a good start, but it's not a silver bullet.
I agree to your other items, though.
- petre 9y agoWe wanted to contribute forest data on Africa back in 2015. It wasn't possible. We'd have to add it via JOSM or the web based editor. So we gave up since it was a no go. Now we just discard the OSM forest data and add our own when updating the map data.
- alexchamberlain 9y agoAre you not violating the licence in this case? Or do you make the new dataset available under the same licence? I think the licence is one of OSM’s big problems.
- rmc 9y ago> It wasn't possible. We'd have to add it via JOSM or the web based editor. That's strange. What were you trying to do? If you convert your data to OSM's relatively simple XML format, you can open that file in JOSM, and just press the upload button. That's what most people do with imports. It's possible to communicate with the OSM API directly and make API calls, but that's essentially what JOSM does. JOSM also has a validator, which can spot some problems with your data.