Support
The GML is rejected by the Cadastre electronic office
Summary
After an MDT update, the GML files of plots and buildings generated by the program stopped being accepted by the Cadastre electronic office, which rejects them saying that they do not comply with the format. The cause is that the area tag began to label the area unit with the superscript character "²" (m²) instead of a normal "2" (m2), a format that the Cadastre XML schema does not accept. This article explains the immediate solution (correcting the character in the file itself) and the definitive solution (updating the plots module and exporting again).
Applies to
MDT 9, MDT 25 and MDT26. The documented cases occurred in MDT 25.
GML export of plots and of buildings/constructions (including the ICUC procedure of the Cadastre electronic office).
Symptoms
The GML files generated by the program cannot be uploaded to the Cadastre electronic office, which warns that they do not comply with the format or that the GML is not valid.
The problem occurs both with the GML of the plot and with that of the building generated by the plot buildings function (in order to process an ICUC).
When trying to reimport into the program those same GML files that have just been generated, MDT reports that they do not exist.
Cause
A program update introduced a change in the way area units are expressed: in the area tag, square metres are labelled with the superscript character "²" (m²) instead of the normal "2". The Cadastre XML schema does not accept that character, so it rejects the file. That same odd character is also what prevents the GML from being reimported into MDT itself.
Solution
Case: correcting the generated file manually (immediate solution)
Open the generated GML/XML file with a text editor.
Find the area tag, of the type
<cp:areaValue uom="m²">: an odd character (the superscript "²") will appear in place of the "2".Replace that superscript "²" character with a normal "2", so that it reads
<cp:areaValue uom="m2">.Save the file. With that change you will be able to upload and validate it at the Cadastre, and also import it back into the program.
Case: updating the plots module (definitive solution)
So that you do not have to correct every file by hand, update the module with the issue already fixed. There are two equivalent ways:
Download the updated installer corresponding to your licence from the Private Area of the website and install it.
Replace the plots module file with the corrected one, with AutoCAD closed:
Download the compressed file of the plots module and unzip it.
Copy the resulting file into the installation folder of your version of MDT, overwriting the existing one. The module name carries the version number:
parcelas9.arxin MDT 9,parcelas25.arxin MDT 25 andparcelas26.arxin MDT26. In one documented case the path wasC:\Program Files (x86)\Aplitop\MDT25\r25x64. Check the actual folder of your installation before copying: it varies with the computer and the version.Make the copy with AutoCAD closed.
You can check that the update has been applied by running the About option, where the new version of the module should appear.
Check the version of the Plots module as well as that of MDT: they are independent and appear separately in About (in one documented case, MDT 25.0.03.01 with Plots module 25.0.08.5).
Export the plot again: the resulting GML will now import and validate at the Cadastre without needing to be edited.
If the problem persists
If the GML is still rejected after updating the module, use the About option to verify that the version of the plots module is the corrected one and that the file was copied with the CAD closed.
If you cannot find the updated installer in the Private Area, or cannot locate the installation folder, contact Aplitop technical support stating your version and your licence.
Category: Cadastre and GML · Level: Intermediate