Page History

V---------------[this is COSTA RICA !!! and Costa Verda]---------------V
^-[this]-V-[is]-V-[COSTA]-V-[RICA]-V-[!!!]-V-[and]-V-[Costa]-V-[Verda]-^
^-[costa]-^-[rica]-^ ^-[costa]-^-[verda]-^
^--[{_geoname_}]---^ ^---[{_geoname_}]---^

Operates On:  Lexical Items with TOKEN and possibly other flags as specified below.

Configuration Parameters

• Parameter
  summary description default cheese name parameter

  
  
  • Explanation

"parameter": "something something"

Example Output

V---------------[this is COSTA RICA !!! and Costa Verda]---------------V 
^-[this]-V-[is]-V-[COSTA]-V-[RICA]-V-[!!!]-V-[and]-V-[Costa]-V-[Verda]-^ 
                ^-[costa]-^-[rica]-^               ^-[costa]-^-[verda]-^ 
                ^--[{_geoname_}]---^               ^---[{_geoname_}]---^ 

Output Flags

Lex-Item Flags:

• SEMANTIC_TAG - Identifies all lexical items that are semantic tags.
• GEONAME- Identifies a geographical location name.

Vertex Flags:

Resource Data

Entity Dictionary Format

The only file that is absolutely required is the geonames dictionary. It is a series of JSON records, typically indexed by entity ID.

Each JSON record represents an entity. The format is as follows:

"_id" : "KGAAJGsBemSwA0nZTLXA",
"id" : 3621815,
"display" : "San Juan",
"patterns" : [
  "San Juan"
],
"tag" : "DDfO1HABPr3bu3tFxDT4",
"fields" : {
  "feature class" : "P",
  "feature code" : "PPL",
  "admin3 code" : "20203",
  "timezone" : "America/Costa_Rica",
  "country code" : "CR",
  "admin1 code" : "01",
  "location" : {
    "lon" : -84.4654,
    "lat" : 10.10676
  },
  "modification date" : "2016-09-07",
  "admin2 code" : "202",
  "dem" : 1093,
  "population" : 0
},
"confAdjust" : 1.0

Fields

• Parameter
  summary An ID normally refering the ID of a database, a document, an API key, not necessary unique name id required true

• Parameter
  summary Tag which will identify any match in the graph, as an interpretation name tag required true

  
  

  • These will all be added to the interpretation graph with the SEMANTIC_TAG flag.

• Parameter
  summary A list of patterns to match in the content name patterns type string array required true

  • Patterns will be tokenized and there may be multiple variations which can match.

    Note
    Currently, tokens are separated on simple white-space and punctuation, and then reduced to lowercase.

• Parameter
  summary What to show the user when browsing this entity name display

  
  

• Parameter
  summary Free space to add extra data in any format supported by JSON name fields type json

GeoName Index

To improve performance especially for every large databases of entities, the entity dictionary is inverted and indexed.

This currently happens in RAM inside the GeoNames stage. An off-line option for pre-inverting the dictionary will be provided in the future.