Could not load POI category configuration from XML when creating POIs.

[demiantres]

The following command

./map-creator.sh europe/albania hd en,de,fr,es 6

crashes with this error output:

``
Jun 09, 2021 5:55:14 PM org.openstreetmap.osmosis.core.Osmosis run
INFO: Osmosis Version 0.48.3
Jun 09, 2021 5:55:14 PM org.openstreetmap.osmosis.core.Osmosis run
INFO: Preparing pipeline.
Jun 09, 2021 5:55:14 PM org.mapsforge.poi.writer.logging.LoggerWrapper log
INFO: POI writer version: mapsforge-poi-writer-master-SNAPSHOT
Jun 09, 2021 5:55:14 PM org.mapsforge.poi.writer.logging.LoggerWrapper log
INFO: POI format specification version: 2
Jun 09, 2021 5:55:14 PM org.mapsforge.poi.writer.logging.LoggerWrapper log
INFO: Loading categories...
Jun 09, 2021 5:55:14 PM org.mapsforge.poi.writer.XMLPoiCategoryManager
SEVERE: Could not load POI category configuration from XML.
javax.xml.bind.UnmarshalException: unexpected element (uri:"http://mapsforge.org/poi-mapping", local:"category"). Expected elements are <{}category>,<{}mapping>
at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext.handleEvent(UnmarshallingContext.java:714)
at com.sun.xml.bind.v2.runtime.unmarshaller.Loader.reportError(Loader.java:232)
at com.sun.xml.bind.v2.runtime.unmarshaller.Loader.reportError(Loader.java:227)
at com.sun.xml.bind.v2.runtime.unmarshaller.Loader.reportUnexpectedChildElement(Loader.java:94)
at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext$DefaultRootLoader.childElement(UnmarshallingContext.java:1119)
at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext._startElement(UnmarshallingContext.java:544)
at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext.startElement(UnmarshallingContext.java:526)
at com.sun.xml.bind.v2.runtime.unmarshaller.SAXConnector.startElement(SAXConnector.java:138)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:228)
at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:199)
at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:140)
at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:145)
at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:154)
at org.mapsforge.poi.writer.XMLPoiCategoryManager.(XMLPoiCategoryManager.java:60)
at org.mapsforge.poi.writer.PoiWriter.(PoiWriter.java:111)
at org.mapsforge.poi.writer.PoiWriter.newInstance(PoiWriter.java:53)
at org.mapsforge.poi.writer.osmosis.PoiWriterTask.(PoiWriterTask.java:66)
at org.mapsforge.poi.writer.osmosis.PoiWriterFactory.createTaskManagerImpl(PoiWriterFactory.java:87)
at org.openstreetmap.osmosis.core.pipeline.common.TaskManagerFactory.createTaskManager(TaskManagerFactory.java:60)
at org.openstreetmap.osmosis.core.pipeline.common.Pipeline.buildTasks(Pipeline.java:51)
at org.openstreetmap.osmosis.core.pipeline.common.Pipeline.prepare(Pipeline.java:112)
at org.openstreetmap.osmosis.core.Osmosis.run(Osmosis.java:86)
at org.openstreetmap.osmosis.core.Osmosis.main(Osmosis.java:37)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:564)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
at org.codehaus.classworlds.Launcher.main(Launcher.java:47)

Jun 09, 2021 5:55:14 PM org.openstreetmap.osmosis.core.Osmosis main
SEVERE: Execution aborted.
java.lang.NullPointerException
at org.mapsforge.poi.writer.XMLPoiCategoryManager.(XMLPoiCategoryManager.java:70)
at org.mapsforge.poi.writer.PoiWriter.(PoiWriter.java:111)
at org.mapsforge.poi.writer.PoiWriter.newInstance(PoiWriter.java:53)
at org.mapsforge.poi.writer.osmosis.PoiWriterTask.(PoiWriterTask.java:66)
at org.mapsforge.poi.writer.osmosis.PoiWriterFactory.createTaskManagerImpl(PoiWriterFactory.java:87)
at org.openstreetmap.osmosis.core.pipeline.common.TaskManagerFactory.createTaskManager(TaskManagerFactory.java:60)
at org.openstreetmap.osmosis.core.pipeline.common.Pipeline.buildTasks(Pipeline.java:51)
at org.openstreetmap.osmosis.core.pipeline.common.Pipeline.prepare(Pipeline.java:112)
at org.openstreetmap.osmosis.core.Osmosis.run(Osmosis.java:86)
at org.openstreetmap.osmosis.core.Osmosis.main(Osmosis.java:37)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:564)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
at org.codehaus.classworlds.Launcher.main(Launcher.java:47)

``

The creation of the map file works fine. What could be the reasons for the POI creation failure?

[devemux86]

Try with Osmosis 0.47.

Testing the following command with Java 11, it works fine.

map-creator.sh europe/andorra ram en,de,fr,es 2

[demiantres]

Same problem. Maybe the problem is caused by the latest snapshot map/poi-writer from https://oss.sonatype.org/content/repositories/snapshots/org/mapsforge/

I will try to find older releases of the plugins.

[demiantres]

I tried different plugin versions (0.15, 0.16) but both fail with the same error. Is there maybe something else to change in the "map-creator.sh" script?

[demiantres]

Removing the following from the "https://github.com/mapsforge/mapsforge/blob/master/mapsforge-poi-writer/src/main/config/poi-mapping.xml" fixes the problem:

xmlns="http://mapsforge.org/poi-mapping" xsi:schemaLocation="http://mapsforge.org/poi-mapping https://raw.githubusercontent.com/mapsforge/mapsforge/master/resources/poi-mapping.xsd"

[devemux86]

The test was done with Osmosis 0.47 and Java 11 on linux and the latest map-writer / poi-writer and everything works fine.
(like we build them at the server all this time)

mapsforge-map-writer-master-20210527.154736-408-jar-with-dependencies.jar
mapsforge-poi-writer-master-20210527.154751-408-jar-with-dependencies.jar
(which are the current 0.16 releases)

You can run the POI command (see the documentation) outside mapsforge-creator.
There could be some issue in the local environment that needs to be fixed.

[demiantres]

I use a complete fresh Ubuntu installation. But removing the namespace definition from the XML file fixes the problem for me.

[demiantres]

On another system it works without problems. Seems to be a local environment issue indeed.

[devemux86]

On another system it works without problems. Seems to be a local environment issue indeed.

What Java distribution and version do they have, AdoptOpenJDK 11 LTS?

[demiantres]

OpenJDK 14. On the other system where it works there is OpenJDK 11 installed (64 versions on both systems).

[hike6688]

Thanks for the link to this discussion
I have tried the tip removing the xmlns , but this did not work.

I switched to Java 11 and poiwriter 0.25
Configuration
Ubuntu 24.04 LTS
java --version
openjdk 11.0.27 2025-04-15
OpenJDK Runtime Environment (build 11.0.27+6-post-Ubuntu-0ubuntu124.04)

I downloaded the last bremen.osm.pbf from geofabrik
and made a new approach to test the osmosis installation

but the unmarshaller error is always there.

``
~/mapsforge-mapcreator$ ../osmosis/bin/osmosis --rb data/bremen.osm.pbf --pw file=data/bremen.poi
Juni 13, 2025 3:31:46 NACHM. org.openstreetmap.osmosis.core.Osmosis run
INFORMATION: Osmosis Version 0.47
Juni 13, 2025 3:31:47 NACHM. org.openstreetmap.osmosis.core.Osmosis run
INFORMATION: Preparing pipeline.
Juni 13, 2025 3:31:47 NACHM. org.mapsforge.poi.writer.logging.LoggerWrapper log
INFORMATION: POI writer version: mapsforge-poi-writer-0.25.0
Juni 13, 2025 3:31:47 NACHM. org.mapsforge.poi.writer.logging.LoggerWrapper log
INFORMATION: POI format specification version: 3
Juni 13, 2025 3:31:47 NACHM. org.mapsforge.poi.writer.logging.LoggerWrapper log
INFORMATION: Loading categories...
Juni 13, 2025 3:31:47 NACHM. org.mapsforge.poi.writer.XMLPoiCategoryManager
SCHWERWIEGEND: Could not load POI category configuration from XML.
javax.xml.bind.UnmarshalException: unerwartetes Element (URI:"http://mapsforge.org/poi-mapping", lokal:"category"). Erwartete Elemente sind <{}category>,<{}mapping>
at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext.handleEvent(UnmarshallingContext.java:714)

``

I want to switch from a old but well running system with Ubuntu 16 and mapsforge 0.8 to a new machine as the old python 2.7 script does not work with python 3.
What is the new configuration you use now on the mapsforge server?
Regards

[devemux86]

@hike6688 Are you sure you removed correctly the xmlns line?
It requires calling an external poi-mapping.xml file in command line.

Also try to download an external Java from https://adoptium.net
Do not use the Java of Ubuntu.

[hike6688]

I did now install java 11 from adoptium.net and made a new try as root
root@Wortmann-Laptop:/home/mfdevelvk/mapsforge-mapcreator# java --version openjdk 11.0.27 2025-04-15 OpenJDK Runtime Environment Temurin-11.0.27+6 (build 11.0.27+6)
but no success
root@Wortmann-Laptop:/home/mfdevelvk/mapsforge-mapcreator# ../osmosis/bin/osmosis --rb data/bremen.osm.pbf --pw file=data/bremen.poi Juni 13, 2025 7:00:19 NACHM. org.openstreetmap.osmosis.core.Osmosis run INFORMATION: Osmosis Version 0.47 Juni 13, 2025 7:00:20 NACHM. org.openstreetmap.osmosis.core.Osmosis run INFORMATION: Preparing pipeline. Juni 13, 2025 7:00:20 NACHM. org.mapsforge.poi.writer.logging.LoggerWrapper log INFORMATION: POI writer version: mapsforge-poi-writer-0.25.0 Juni 13, 2025 7:00:20 NACHM. org.mapsforge.poi.writer.logging.LoggerWrapper log INFORMATION: POI format specification version: 3 Juni 13, 2025 7:00:20 NACHM. org.mapsforge.poi.writer.logging.LoggerWrapper log INFORMATION: Loading categories... Juni 13, 2025 7:00:20 NACHM. org.mapsforge.poi.writer.XMLPoiCategoryManager <init> SCHWERWIEGEND: Could not load POI category configuration from XML. javax.xml.bind.UnmarshalException: unerwartetes Element (URI:"http://mapsforge.org/poi-mapping", lokal:"category"). Erwartete Elemente sind <{}category>,<{}mapping> at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext.handleEvent(UnmarshallingContext.java:714)

[devemux86]

I don't know why some of you have these problems. All this time here everything works correctly.

My latest tests are on Debian with Java 17 and 21 (internal and external) with Osmosis 0.47
and both map-writer and poi-writer work correctly.

[hike6688]

I will try java 21 from adoptium.net.

Which Debian distribution is used on the server?

The laptop I use is an older machine which I use only for testing.
Maybe I have to try with another Linux distribution.

[hike6688]

Now it works
Configuration
0. Ubuntu 24 LTS

1. java --version Temurin
   openjdk 17.0.15 2025-04-15 OpenJDK Runtime Environment Temurin-17.0.15+6 (build 17.0.15+6) OpenJDK 64-Bit Server VM Temurin-17.0.15+6 (build 17.0.15+6, mixed mode, sharing)
2. Osmosis Version 0.47
3. mapsforge-poi-writer-0.25.0
4. I created a small poi-mapping file poi-mapping_only_amendities2.xml
   and changed the file head of the poi-mapping.xml as Demirantes pointed out.
   Solved the problem at last.

Line 2 in the poi-mapping.xml is now:
<category xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" title="root">

or
<?xml version="1.0" encoding="UTF-8"?> <category xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" title="root"> <!-- xmlns="http://mapsforge.org/poi-mapping" xsi:schemaLocation="http://mapsforge.org/poi-mapping https://raw.githubusercontent.com/mapsforge/mapsforge/master/resources/poi-mapping.xsd"> --> <!-- http://wiki.openstreetmap.org/wiki/Map_Features -->
5. ../osmosis/bin/osmosis --rb data/bremen.osm.pbf --pw file=data/bremen.poi tag-conf-file=data/poi-mapping_only_amendities2.xml
solved the problem
home/mfdevelvk/mapsforge-mapcreator# ../osmosis/bin/osmosis --rb data/bremen.osm.pbf --pw file=data/bremen.poi tag-conf-file=data/poi-mapping_only_amendities2.xml Juni 15, 2025 12:31:46 PM org.openstreetmap.osmosis.core.Osmosis run INFORMATION: Osmosis Version 0.47 Juni 15, 2025 12:31:47 PM org.openstreetmap.osmosis.core.Osmosis run INFORMATION: Preparing pipeline. Juni 15, 2025 12:31:47 PM org.mapsforge.poi.writer.logging.LoggerWrapper log INFORMATION: POI writer version: mapsforge-poi-writer-0.25.0 Juni 15, 2025 12:31:47 PM org.mapsforge.poi.writer.logging.LoggerWrapper log INFORMATION: POI format specification version: 3 Juni 15, 2025 12:31:47 PM org.mapsforge.poi.writer.logging.LoggerWrapper log INFORMATION: Loading categories... Juni 15, 2025 12:31:47 PM org.mapsforge.poi.writer.logging.LoggerWrapper log INFORMATION: Adding tag mappings... Juni 15, 2025 12:31:48 PM org.mapsforge.poi.writer.logging.LoggerWrapper log INFORMATION: Creating POI database... Juni 15, 2025 12:31:48 PM org.openstreetmap.osmosis.core.Osmosis run INFORMATION: Launching pipeline execution. Juni 15, 2025 12:31:48 PM org.openstreetmap.osmosis.core.Osmosis run INFORMATION: Pipeline executing, waiting for completion. Juni 15, 2025 12:31:48 PM org.mapsforge.poi.writer.logging.LoggerWrapper log INFORMATION: Processing nodes... Juni 15, 2025 12:31:55 PM org.mapsforge.poi.writer.logging.LoggerWrapper log INFORMATION: Processing ways... Juni 15, 2025 12:32:18 PM org.mapsforge.poi.writer.logging.LoggerWrapper log INFORMATION: Committing... Juni 15, 2025 12:32:18 PM org.mapsforge.poi.writer.logging.LoggerWrapper log INFORMATION: Filtering categories... Juni 15, 2025 12:32:18 PM org.mapsforge.poi.writer.logging.LoggerWrapper log INFORMATION: Writing metadata... Juni 15, 2025 12:32:19 PM org.mapsforge.poi.writer.logging.LoggerWrapper log INFORMATION: Post-processing... Juni 15, 2025 12:32:20 PM org.mapsforge.poi.writer.logging.LoggerWrapper log INFORMATION: Added 13.067 POIs. Juni 15, 2025 12:32:20 PM org.mapsforge.poi.writer.logging.LoggerWrapper log INFORMATION: Estimated memory consumption: 38,5MB Juni 15, 2025 12:32:20 PM org.openstreetmap.osmosis.core.Osmosis run INFORMATION: Pipeline complete. Juni 15, 2025 12:32:20 PM org.openstreetmap.osmosis.core.Osmosis run INFORMATION: Total execution time: 34095 milliseconds.

All my old seamark_poi_tagmapping.xml now run if I do step 4 changing line 2 in all this files.

[devemux86]

A problem with such solution is that the validation of the xml in the editors
cannot work if we remove the xsd declaration in the xml.

Also important is why suddenly and only some users need such solution.