[osmosis-dev] Msg error with osmosis when bboxing

Frederik Ramm frederik at remote.org
Sun May 13 15:03:50 BST 2012


Hi,

On 05/13/2012 02:56 PM, Séverin MENARD wrote:
> I have a small issue with osmosis. Already post this message on OSM help
> (no answer)

I saw your question there but had no idea what the problem could be. The 
message you are seeing would typically occur if something is logically 
wrong with your Osmosis command line, e.g. you read a file but don't 
write the results to anywhere or so.

For example, if I enter

osmosis --read-xml file="dummy"

then I get the message

The following named pipes () and 1 default pipes have not been 
terminated with appropriate output sinks.

Osmosis wouldn't even try to read the "dummy" file.

If, however, I run your command on my machine:

osmosis --read-xml file="D:/OSM/Salvador/brazil.osm" --bounding-polygon 
file="D:/OSM/Salvador/Bahia_contour.poly" --write-xml 
file="D:/OSM/Salvador/bahia.osm"

then I get the message

Unable to read XML file D:/OSM/Salvador/brazil.osm

because Osmosis has correctly parsed the command line and tried to 
execute it. So there's nothing wrong with your command line as far as I 
can see.

I therefore think that something in your osmosis.bat must be broken, 
leading to Osmosis being called with not enough parameters or something 
crazy. Maybe you should add an "echo" statement to your osmosis.bat so 
you can see what command is run. (It is also possible, but less likely, 
that you have some strange Java installation that ruins command line 
arguments.)

Bye
Frederik

-- 
Frederik Ramm  ##  eMail frederik at remote.org  ##  N49°00'09" E008°23'33"



More information about the osmosis-dev mailing list