I think it is useful to be able to split two (or more) files simultaneously, but as part of the same job - same mapid, description, etc. Not only contour lines, but grid lines or latitude/longitude. Roger On 15/12/2012 17:23, GerdP wrote:

Hi all,

while documenting the new splitter parms I wondered if anybody needs to be able to split two or more files using a command like java -jar splitter.jar file1.osm file2.osm

This is not documented but implemented. What's the expected result if the two files overlap or if the two files cover two area that are far away from each other? I remember seeing this used with contour lines. Is that still needed? Did anybody test that with --keep-complete?

Also, why is it needed to be able to read from stdin? cat file.osm | java -jar splitter.jar --split-file=areas.list

Would it be okay to drop these two undocumented features?

Gerd

-- View this message in context: http://gis.19327.n5.nabble.com/splitter-input-file-handling-tp5740516.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

-- ------------------------------------------------------------------------ Roger Calvert ------------------------------------------------------------------------

On Sat, Dec 15, 2012 at 09:23:37AM -0800, GerdP wrote:

Also, why is it needed to be able to read from stdin? cat file.osm | java -jar splitter.jar --split-file=areas.list

I guess this ceased to be useful when everyone moved from *.osm.bz2 to a 'native' binary format (*.osm.pbf or *.o5m). I used to have a pipe like this: bzip2 -dc < file.osm.pbf | perl -e '...' | java -jar splitter.jar ...

Would it be okay to drop these two undocumented features?

I do not mind dropping the ability to read from standard input. Best regards, Marko