Output extensions

Aspose.GIS Product Family
1

Hi Alexander,

1.I need some clarification for my customer:
image.png (26.0 KB)

2**.What will be in target output folder ?**
When converting data from the source format to the target format, only the mandatory files are converted and placed in the target output folder ? is it right ? or these the files for GIS Convert.Layer operation only?
if I have others files like .txt or optionals like .prj for shapefile format they will be in output?
Example:Gdb to Shapefile:
image.png (2.4 KB)

3.What outputs files of the following target format, sometimes I see not only the mandatories files?
MapInfo Interchange
MapInfo Tab -sometimes only .mif sometimes .mif and .mid ?
Shapefile - I see also optional files

Thanks

2

Dear customer,

Thank you for the detailed questions. I’ll address each point regarding the files that are placed in the target output folder when you run a conversion with the GIS Convert → Layer operation.

1. What is written to the target output folder?

The conversion engine always writes the mandatory files that are required for the target format to be a valid dataset.
In addition, any optional files that exist in the source dataset and are supported by the target format are copied over automatically.

So the output folder can contain:

Target format Mandatory files Optional files that may also be written
Shapefile .shp, .shx, .dbf .prj, .cpg, .xml, .qix, .sbn, .sbx, … (only if they exist in the source GDB and the format supports them)
MapInfo Tab / Interchange .tab (or .mif for Interchange) .dat, .map, .id, .mid (attribute file), .tab‑related auxiliary files – written when present in the source
GeoPackage .gpkg none (all data are stored inside the single file)
File Geodatabase .gdb folder structure none (the whole folder is the dataset)

The GIS Convert → Layer operation guarantees that the mandatory set is always produced; optional files are included on a best‑effort basis.

2. “Only the mandatory files are converted?” – clarification

For a given conversion the engine must create the mandatory files; otherwise the target dataset would be unusable.
If the source dataset contains optional companion files (e.g., a .prj for a shapefile, a .mid for a MapInfo Interchange file, a .cpg for character encoding, etc.) and the target format can store that information, the engine will copy those files to the output folder as well.

Therefore:

  • GDB → Shapefile – you will always get .shp, .shx, .dbf.
    If the source feature class has a projection defined, a .prj will be written.
    Any other auxiliary files that exist (e.g., .cpg, .xml) are also copied.

  • MapInfo Interchange (MIF/MID) – the .mif file is mandatory.
    If the source contains attribute data, a corresponding .mid file is generated; otherwise only the .mif appears.

3. Why do I sometimes see extra files for the same target format?

The presence of optional files depends on the source data and on whether the target format can represent that information:

  • Shapefile – projection (.prj), character set (.cpg), spatial index (.qix), etc., are optional. They appear only when the source dataset includes that information.
  • MapInfo Tab – the .dat and .map files hold geometry and attribute data; the .mid file is optional and appears only when attribute data are present in the source.

If the source does not contain a particular optional component, the conversion will not create an empty placeholder for it.

4. Controlling the inclusion of optional files

At the moment the GIS Convert app does not expose a separate “include optional files” toggle; the behavior described above is the default. If you need to guarantee that a specific optional file (e.g., a .prj) is always present, make sure it exists in the source dataset before running the conversion.

5. Quick checklist for your customer

Source → Target Expected mandatory files Optional files that may appear
GDB → Shapefile .shp, .shx, .dbf .prj, .cpg, .xml, .qix, …
GDB → MapInfo Tab .tab .dat, .map, .id, .mid (if attributes)
GDB → MapInfo Interchange .mif .mid (if attributes)

If you observe a missing optional file that you expected, verify that the source dataset actually contains it.

Please let me know if you need a concrete example (e.g., a small test dataset) or if you have any additional requirements regarding the handling of optional files. I’m happy to help further.

3

Hi Alexander,
Can you please verify?
In addition if in source there is .txt file that not belong to format it will be in target ?
image.png (19.8 KB)
Waiting to your answer.
Thanks

4

Hi, @danies8

Yes

No

Correct

Dani, tomorrow I have day off.
I will back to work on Monday.
Thanks for understanding!