Jochen123 wrote > > > > Just the geometries is not enough. We also need the tags in some form, > because > part of the multipolygon assembly is deciding which tags from the relation > and which tags from the member ways make it to the output. > >
I thought about focusing on geometry first since this is the more complicated part. But sure for tags it gets very complicated if we consider diff files too. Jochen123 wrote > > > Input as .osm is good. But the output should not be on a wiki page but in > some > format so that it can be used for automated checks. I think the whole > thing > should probably be in a git repository. > > Maybe a subdirectory for each test case which contains the .osm input > file, > a .wkt output file, a .tags output file and a .result output file or so > that > has information whether the test should succeed or fail. Maybe other > files, > too with more detailed information if that turns out to be needed. Plus a > README in every directory describing the test case to the developer. > > I like that idea. With the directory structure we can add .osc file to the directories as well so that we can check proper diff file handling after the initial import... I will try to get something like that ready as a demo -- View this message in context: http://gis.19327.n5.nabble.com/New-OGR-driver-to-read-OpenStreetMap-osm-pbf-files-tp5715906p5716442.html Sent from the Developer Discussion mailing list archive at Nabble.com. _______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
