Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

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, DOC, DOCX, RTF, XLS, XLSM, XLSX, PPT, PPTX, XPS

MS Word and Excel 97-2003 and later versions are supported.

(tick) Tagging

(tick) Masking

Libre Office, Open Office

ODT, ODP

(tick) Tagging

(tick) Masking

PDF

PDF files can be automatically OCRed if they do not contain text information. The e-Signature information of e-Signed PDFs is also read.

(tick) Tagging

(tick) Masking

(tick) E-Signature

(tick) OCR

E-Mail

Servers: Google Mail, Yahoo Mail, Office 365, POP3, IMAP, Exchange,

File: PST, OST

E-mail and all attachments

(tick) Classification for Office 365

Pictures, Videos and Audio Files

JPG, JPEG, PNG, TIF, TIFF, GIF, BMP, JP2

M2TS, MOV, MP4, MP3, OGG, AVI, 3GP, ASF, FLV, MKV, MPG, MPEG,OGV,WMV, DIVX,DAT,WMV,XVID,X264,WMV1,SEC

(tick) Tagging

(tick) FacePro

(tick) ImagePro

(tick) SpeechTotext(3rd party solution)

Social Media and Web

HTML, HTM, MHT

RSS

Twitter, Instagram, Facebook

Databases

Oracle, Postgres, DB2, SQLServer, Postgres, Mongo, Cassandra,

File based: Access, SQLite, MDB, ACCDB, ACCDE, ACDDT, ACCDR

(tick)Files embedded or linked to databases

(tick)Texts embedded in databases

(tick)Spatial information (Oracle Spatial, Postgres..)

Compressed Files

ZIP, ZIPX, RAR, 7Z, 7ZIP

All archives and files contained within these archives

CAD and GIS formats

Autocad, Netcad, Microstation, ArcGIS, Google Earth

DWG, NCZ, DGN, DXF,SHP, KML, 

GeoTIFF, ECW, SID, IMG

GEODI360: SRTMAP,NMEA,GPX,GPS,FLIGHTPLAN,FPL,IGC,XML

Netcad: NCZ, KSE, KSP , DRE , CKS, KAP, DRK

Others

TXT, XML,

MPP, Microsoft Project Manager

UDF, Uyap Document Format

EYP, E-Correspondence Package

MOBIDI, MOBIDI Office

GEODI Url

With the GEODI Url file format it is possible to create text and location for a specific web link. It can be a youtube link, a web page. GEODI Url does not index page content.

url=https://www.youtube.com/watch?v=O7X3TG8bfoQ

Türkçe=Bu videomuzda GEODI'nin yol firmaları ve kurumlar için faydalarını göreceksiniz.

English=This video shows how GEODI is usefull for road companies and authorities.

Geom=If you have Geometry in WKT format, it is enough to enter Geometry in Geographic WGS84 datum. For example POINT(33 42), LINESTRING (30 10, 10 30, 40 40).

geomdisplayname=We determine the label of the geometry on the map.

For WKT, please see What is WKT Geometry?

For WKT Drawing → https://arthur-e.github.io/Wicket/sandbox-gmaps3.html

 Sample *.geodiurl File

Defining External Metadata for Files

You can define information that is 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 when you want to associate a person, parcel or other value.

(warning) File Name "World Map.DWG" , in this case the meta file name should be "World Map.DWG.meta.xml".

Any content is used to define structured data. This is just 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 shapes.

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"
}

 

TargetExtension: Target file extension. Optional. If not defined, name matching connection with all files will be checked.

MainFileFormat: Specifies how to check for name matching with files. [FILE] indicates the file name [EXT] indicates the extension.

IgnoreMetaFile: Allows to omit metafiles. Optional. If left blank, the metafile is also indexed separately by GEODI.

GroupElement: Group node name in XML.

KeyElement: Key node name under the group node. Optional. Projection expression received with KeyElement is always considered as projection. It can be EPSG:... WKT.

  • projection : Projection in WKT or EPSG must be written in the META_VALUE field.

  • geom : WKT geometry must be written in the META_VALUE field.

  • previewbase64:base64 The preview image can be forced by throwing an image.

  • forcedsummary: can be forced to preview the summary to be displayed in all searches.

  • forcedviewurl: The address to be used for the viewer (to open the content) can be set.

  • permit: It is an authorized user list. It 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-22155deny:Prohibited 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


ValueElement: Value node name under the group node.


AreaElement: Field type value under the group node. Determines its position in the index. The AreaElement value can be Header or Content. Content is also seen in the summary content. The default value is Header. If the Content value is used, it is displayed in the summaries.

 

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.

<metadata>
	<META_NAME>Note</META_NAME>
	<META_VALUE>Look at the beauty of the cats in this photo.</META_VALUE>
	<META_AREA>Content</META_AREA>
</metadata>

Geometry Example:

It can also be used to add Geometry to any content.

<metadata>
	<META_NAME>GEOM</META_NAME>
	<META_VALUE>WKT GEOMETRY definition</META_VALUE>
</metadata>

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

<Meta>
       <metadata>
          <META_NAME>permit</META_NAME>
          <META_VALUE>geodi:deneme,UserGroup_a1224,dece\yz,S-111-22155</META_VALUE>
       </metadata>
       <metadata>
        <META_NAME>deny</META_NAME>
        <META_VALUE>geodi:guest</META_VALUE>
       </metadata>
</Meta>

 

  • No labels