Supported Formats
- Dece Translate (Unlicensed)
- Arda Ülgü (Unlicensed)
- serdar ak
GEODI supports over 200 formats (support may vary depending on your license)
GEODI reads text information, contact information, and other metadata within each format. It becomes searchable. The specified formats can be selected separately in the GEODI search interface, and, for example, only PDFs can be searched.
Microsoft Ofis
Word, Excel, PowerPoint, Visio, DOC, DOCX, RTF, XLS, XLSM, XLSX, PPT, PPTX, XPS
MS Word and Excel 97-2003 and later versions are supported.
Labelling
Masking (Permanent or Dynamic)
Libre Office, Open Office
ODT, ODP
Labelling
Masking
PDF files can be automatically OCRed if they do not contain text information. The e-Signature information of e-Signed PDFs is also read.
Labelling
Masking (Permanent or Dynamic)
E-Signature
OCR
Sample *.geodiurl File
Defining External Metadata for Files
You can define information not included in the file as metadata with an XML with the extension "<filename.extension>.meta.xml" in the same place as the file. You can use this method when you want to define a projection for CAD files with unknown projection or to associate a person, parcel, or other value.
File Name "World Map.DWG" , the meta file name should be "World Map.DWG.meta.xml".
Any content is used to define structured data. This is one of the many ways to define structured data in GEODI.
You can specify the metafile structure and naming conventions of metafiles in a separate jsettings file. In this way, it is also possible to support metafiles of different forms.
This definition file must be in the [.\Settings\AttributeProvider\XMLMeta] directory. GEODI must be restarted if the file changes.
In this example, files with *.meta.xml extension are associated with *.tif files. The XML file contents are expected to be as follows.
{
"TargetExtension":".tif",
"MainFileFormat":"[FILE][EXT].meta.xml",
"IgnoreMetaFile":".meta.xml",
"GroupElement":"metadata",
"KeyElement":"META_NAME",
"ValueElement":"META_VALUE",
"AreaElement":"META_AREA"
}
Sample Meta XML File
<metadata>
<META_NAME>Column</META_NAME>
<META_VALUE>Value</META_VALUE>
</metadata>
<metadata>
<META_NAME>Column</META_NAME>
<META_VALUE>Value</META_VALUE>
</metadata>
<metadata>
<META_NAME>Column</META_NAME>
<META_VALUE>Value</META_VALUE>
<META_AREA>Content</META_AREA>
</metadata>
It is used to define projections for non-georeferenced files such as DWG. The coordinates in the DWG must be in the corresponding projection.
EPSG or WKT Projection Example
<metadata>
<META_NAME>Projection</META_NAME>
<META_VALUE>EPSG:4326</META_VALUE>
</metadata>
<metadata>
<META_NAME>Projection</META_NAME>
<META_VALUE>WKT Projeksiyon</META_VALUE>
</metadata>
Content Example:
It is used to add text to content. You can use it to annotate an image or video file. Other text in the content defined here is added to the information. The AreaElement value can be Header or Content. Content is also seen in the summary content. The default value is Header.
Geometry Example:
It can also be used to add Geometry to any content.
Authorization Based Content Display Example:
Works in addition to standard authorization. (LDAP authorization is on and we have given one more authorization with meta. the two merge. If a file is forbidden to a user in LDAP, meta.xml cannot exceed it. )
Permit is authorized, Deny is forbidden user list. can contain user id, group id, provider group id list. Information about the active user can be retrieved from /api. Example : geodi:deneme, ldap..., UserGroup_a1224, S-111-22155