Convert FILEGDB to GML
Turn FILEGDB files into GML. A GML 3.2 document with one feature type holding the features and their attributes, in the source's coordinate system and without a separate schema file.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop FILEGDB files on the dialor turn it to pick what to do
Map features as one GML 3.2 file.Your zipped geodatabase becomes a single GML document with every feature and its attributes.
What you get
One GML 3.2 file with one feature type that holds all the features and their attributes. The features stay in the coordinate system of the source, and no separate schema file is written.
If the geodatabase has several layers, they are joined into one feature type. A layer column names the layer each feature came from.
What changes
Some features may have heights while others do not. The ones without a height get a height of 0.
Lists and nested values have no plain place in the output, so they become JSON text.
Going back
To turn GML into a geodatabase again, use GML to FILEGDB. For other GML conversions, see every GML conversion.
FILEGDB and GML.What each format is.
The formats
Esri File Geodatabase
An ArcGIS file geodatabase, the .gdb folder of feature classes, zipped to send as one file.
- Extensions
- .gdb.zip
- MIME type
- application
/x -filegdb +zip - Kind
- Text and data
GML
Geography Markup Language, the OGC's XML for map features, as WFS services send it.
- Extensions
- .gml
- MIME type
- application
/gml +xml - Kind
- Text and data
In your code.The same FILEGDB to GML conversion through the API, for your app or your agent.
$ cv convert report.gdb.zip report.gml$ cv convert report.gdb.zip report.gmlQuestions.What people ask about FILEGDB to GML.
One. All layers end up in the same GML file.
Each feature has a layer column with the name of its source layer.
No. The features stay in the coordinate system of the source.
No. The output is a GML document without a separate schema file.