OpenStreetMap
Well, an area that I mapped on paper but hadn't put in seems to have been "imported".
The import gets a giant FAIL from me, if that is what it is. Many streets are disjoint, Names of streets are every block and so on. If this is the new face of OSM, I'll go back to Google maps with all of their horrible warts.
I've only checked one spot. I hope it's not like this all over.
Anyways, to add insult to injury, Potlatch isn't loading the area, so I can't even fix it. I'm not sure if it's because of too many objects, or if there is some bad data, or just server load, or what.
Diskuse
Komentář od andrewpmk z 16. 06. 2009 v 19:06
This is the import of the GeoBase National Road Network. Please see osm.wiki/GeoBase_Import for details.
The names on every block are an artifact of the process by which the data was imported. Please do not combine ways to get rid of this as this will delete data which will allow future updates to be added to the GeoBase data. Hopefully a future version of the renderers will be intelligent enough to not show names on every block like this.
Streets from the GeoBase data are not automatically connected to the existing data. This has to be fixed manually - I can start on this if you tell me what area you would like fixed. It is probably easier to do this in JOSM. Furthermore, the data is likely to contain errors, and one way streets are missing.
For more information you should talk to stevens who is doing the bulk of the GeoBase import.
Komentář od geobase:acrosscanadatrails z 17. 06. 2009 v 02:01
Thanks Andrew, you answered it much better than i could :)
Please also let me know what area your working on, so i can create a sample area of the CanVec data (lots of other map features) so you can look at. Hopefully you will find errors better than i can.
Komentář od daveemtb z 17. 06. 2009 v 11:30
I don't know what to think of these various dataset imports. On the one hand, it obviously helps make OSM more complete. On the other hand I have to admit, if the area I have mapped (my town and a nearby town) was overwritten with an import, I would be hugely hacked off, having spent the best part of two years mapping it. In my opinion, these imports shouldn't replace existing OSM data.
Komentář od chillly z 17. 06. 2009 v 12:47
Importing data is a short cut, but not as good as gathering data on the ground. Overwriting hand gathered data is bad form. This business of not amending imported data to allow a later import is also very dubious - how do we encourage people to improve the data if you don't want them edit it? Never mind smarter renders - why not smarter imports?
Komentář od daveemtb z 17. 06. 2009 v 12:52
Yeah, I agree. Unless there is other data such as speed limits, road type, etc, that varies between segments, I don't think it is reasonable to expect people not to combine them. OSM data is going to get changed. It is not possible to preserve a link to the data source.
And even if it was possible, is it desirable? What if I decide a road is named incorrectly in the Geobase import, and correct it? Then someone imports a newer geobase dataset, and uncorrects my edit.
I think I agree with chilly that imports should be seen as a shortcut, and not something to use where existing data is already in OSM.
Komentář od OliverLondon z 17. 06. 2009 v 14:26
If I understand the OP correctly, this area was not in OSM. It had been mapped on paper but not yet uploaded. Some data is better than no data, although it must be free to be fixed up however the OSM editors think best.