I am having an issue with importing some GML files provided by the Ordnance Survey in GB. Some of the node values take the following form: xlink:href="somevalue"; for example:
When these are imported, all the values in the table for the affected column (e.g. the columns endNode and startNode) are NULL. All other nodes import fine.
For niche uses like this, Manifold can read through GDAL/OGR. What happens when you try that?
Thanks. On reflection, I think it's better that I use dedicated tools that are available to import the dataset into PostgreSQL and access it in Manifold from there.
PostgreSQL is certainly cool, but don't those tools use GDAL as well for such imports?
There's a QGIS package specifically to import Ordnance Survey MasterMap into PostgreSQL that does the job very efficiently:
What it's using under the hood I don't know.
It uses GDAL. You can see that from the source code to it at https://github.com/lutraconsulting/ostranslator-ii
if not self.process.waitForStarted():
raise Exception('Failed to start process. Please ensure you have gdal/ogr2ogr installed')
Have you tried the GDAL dataport in Manifold?
Sounds like a direct import into Manifold would be easier than to first install PostgreSQL, and then launch QGIS, use a plug-in to import the data into PostgreSQL, and then connect to that from Manifold.
I tried the GDAL dataport and it drops the columns that Manifold had imported with NULL values. Incidently, this is exactly the same as happens when opening the files in QGIS via add vector (which presumably uses GDAL) - some columns are missing from the data. In contrast, when using OS Translator II all fields are present in the relevant PostgreSQL table.
Yes, QGIS depends on GDAL.
You might want to look into the OS Translator II source to see how it uses GDAL. Note that there's been a lot of discussion in the GDAL community about xlink:href in GML files. That also could be a source of useful tips for how to use GDAL to acquire the field you want.