Hello Gerhard,
no, you do not need to define a plugin.xml. It is already included in
the mapfile-writer plugin. Unless you want to write your own plugin, you
do not need to care.
However, it seems that you are trying to read a XML-file (map1.osm) with
the osmosis protocol buffer reader (option --rb). Please use the option
- --rx to read a XML-file and make sure that it includes a bounding box
definition (otherwise use the bbox option of the mapfile-writer plugin).
Please have a look at
http://wiki.openstreetmap.org/wiki/Osmosis/Detailed_Usage for the
detailes usage of osmosis.
Best regards,
J�rgen
- --
J�rgen Bro�
Institute of Computer Science
Freie Universit�t Berlin
Takustr. 9
14195 Berlin, Germany
Phone: +49 30 838-75108
email: juerge...@fu-berlin.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJNR8zrAAoJELhzyv13y+u9o5oIAKpFJ32cBgX6WDKSo/c/iNSV
Re2q4pupWT/bnzlJyoivOheGjoEqYvVTLrGXIzjuyszPEiJ5A9BwBaRxPJRIwDau
c5nhIQfI1kSA3sJ8yYtCcxbyL9hGchHVupmlhZZ1uGFOB+3+pQ2XJSCUtM07UfPV
mNIcJXT7ybrPBParh/8lNUieIMX86rmMDpbu351jNMrPrF5Svg0Zm8sdVXpk9Wn5
h/zu6fj9JMdDyQj//NsgjzXE/Hawr5NXA3JGXufWj1BrBnTk/EiFO/mkRWDffsv7
NCRCLO65o5l2EveB+7E86G7LK3F0SB3+fxi1pP9GQbWDvunoEpi72UrIpiO9/W0=
=mHPO
-----END PGP SIGNATURE-----
it seems that the osmosis installation itself is somehow misconfigured.
It seems that the manifest of any plugin (which is defined in xml) is
not read properly, since a required SAX-Parser cannot be loaded.
* Which version of Java are you using? What does 'java -version' tell you?
* Which steps did you perform in installing osmosis?
The XML that is produced by the OSM website lacks a bounding box
definition, so you need to add it via the bbox option when you run the
mapfile-writer plugin.
You can get OSM-data for lots of regions from Geofabrik
(http://download.geofabrik.de/). My advice is to use the protocol-buffer
format (*.pbf) as it is more compact and faster to process.
(Be aware that also the osm.xml files you download from Geofabrik lack a
bounding box definition.)
Best regards,
Jürgen
Am 01.02.2011 10:37, schrieb GerhardS:
> Thank you Jürgen,
>
> yes map1.osm is an xml file, containing this root node: <osm
> version="0.6" generator="CGImap 0.0.2">. I exported it from
> openstreetmaps web page (as open streetmap xml file). But still with --
> rx I get the same error with the same callstack displayed. Maybe this
> kind of xml file is not what osmosis expects. Even "bin\osmosis --rx
> file=map1.osm --wn" returns that same error, so it doesn't concern the
> plugin.
> So were do I get valid input files for osmosis from? The nicest
> solution would be to specify only a bounding box and get the data
> directly from the open streetmap web server. Where do I get *.osm
> files from?
>
> Thank you
> Gerhard
>
> On 1 Feb., 10:05, Jürgen Broß <juergen.br...@fu-berlin.de> wrote:
> Hello Gerhard,
>
> no, you do not need to define a plugin.xml. It is already included in
> the mapfile-writer plugin. Unless you want to write your own plugin, you
> do not need to care.
>
> However, it seems that you are trying to read a XML-file (map1.osm) with
> the osmosis protocol buffer reader (option --rb). Please use the option
- Zitierten Text anzeigen -
--
Jürgen Broß
Institute of Computer Science
Databases and Information Systems
Freie Universität Berlin
Takustr. 9
D-14195 Berlin, Germany
phone: +49 30 838-75108
email: juerge...@fu-berlin.de
missed your last mail. So forget the first part of my last mail...
Your guess is right: The huge size of the map file is due to the
memory-mapped I/O problem under Windows (see fixed issue 41). The new
version of the writer will work properly under Windows. You will also
have an option (type=hd) that allows you to use the hard disk (instead
of main memory) as temporary storage device during map creation. So you
won't exhibit the OutofMemoryException any more. As a workaround you can
adjust the available memory by setting 'JAVACMD_OPTIONS="-Xmx1500m' in
'bin/osmosis' script. Replace '1500m' with a reasonable amount of memory.
You can also checkout the current version from our public SVN. This will
work nicely.
The next release which will include the new mapfile-writer version will
be published in a few days. So stay tuned. We will announce the release
on this mailing list.
Best regards,
Jürgen