Uses of Class
org.opensextant.ConfigException
Packages that use ConfigException
Package
Description
Extraction Fundamentals
FlexPat -- A Pattern Definition & Testing Library
Language Detection
Xponents Output Formatting using GISCore
-
Uses of ConfigException in org.opensextant.extraction
Methods in org.opensextant.extraction that throw ConfigExceptionModifier and TypeMethodDescriptionvoidExtractor.configure()Configure an Extractor using defaults for that extractor.voidConfigure an Extractor using a config file named by a path.voidConfigure an Extractor using a config file named by a URL. -
Uses of ConfigException in org.opensextant.extractors.flexpat
Methods in org.opensextant.extractors.flexpat that throw ConfigExceptionModifier and TypeMethodDescriptionvoidAbstractFlexPat.configure()Configures whatever default patterns file is named.voidAbstractFlexPat.configure(InputStream strm, String name) voidConfigure using a particular pattern file.voidConfigure using a URL pointer to the pattern file. -
Uses of ConfigException in org.opensextant.extractors.langid
Methods in org.opensextant.extractors.langid that throw ConfigExceptionModifier and TypeMethodDescriptionvoidLangDetect.initLangId()Taken straight from LangDetect example NOTE: /langdetect/profiles must be a folder on disk, although I have a variation that could work with JAR resources.Constructors in org.opensextant.extractors.langid that throw ConfigExceptionModifierConstructorDescriptionDefault use requires you unpack LangDetect profiles here: /langdetect-profilesLangDetect(int textSz) If you anticipate working with short text - queries, tweets, excerpts, etc.LangDetect(int textSz, String profiles) LangDetect(String profiles) -
Uses of ConfigException in org.opensextant.output
Methods in org.opensextant.output that throw ConfigExceptionModifier and TypeMethodDescriptionprotected voidGISDataModel.addAdditionalAttributes(org.opensextant.giscore.events.Feature row, Map<String, Object> rowAttributes) If the caller has additional data to attach to records, allow them to add fields to schema at runtime and map their data to keys on GeocodingResult Similarly, you could have Geocoding row-level attributes unique to the geocoding whereas attrs on GeocodingResult are global for all geocodings in that result set.voidAdds the field.voidvoidvoidAdd a field key to the field order; Caller must also be responsible for ensuring field is valid and exists in Schema.voidList<org.opensextant.giscore.events.Feature>GISDataModel.buildRows(int id, Geocoding g, TextMatch m, Map<String, Object> rowAttributes, ExtractionResult res) Builds a GISCore feature array (rows) from a given array of TextMatches; Enrich the features with record-level attributes (columns).protected voidCSVFormatter.buildSchema()Create a schema instance with the fields properly typed and orderedprotected voidCSVGenericFormatter.buildSchema()Create a schema instance with the fields properly typed and orderedprotected org.opensextant.giscore.events.SchemaGISDataModel.buildSchema(String jobName) Create a schema instance with the fields properly typed and ordered.protected org.opensextant.giscore.events.SimpleFieldGets the field.static org.opensextant.giscore.events.SimpleFieldvoidAbstractGenericFormatter.removeField(String f) Removes the field.voidCSVFormatter.removeField(String f) voidGISDataFormatter.removeField(String fld) voidGISDataModel.removeField(String fld) Removes the field.voidResultsFormatter.removeField(String f)