Release 0.07.5

Updated the code for the new OpenTravelData (OPTD) data format (Geonames coordinates
have been added)

Release 0.07.4

FindBoost.cmake now supports older CMake versions

Release 0.07.3

OPENTREP_SAMPLE_DIR is now specified

Release 0.07.2

• Merged the trunk and releases branches to master, so as to get a standard setup
• The default branch is now master
• The versioning scheme follows the one on the releases branch before, i.e., the version number is incremented just before tagging the Git repository

Release 0.07.1

Improved the release of Python libraries and scripts (e.g., following Fedora packaging guidelines, and it works well with pipenv)

Release 0.07.0

• Support of several deployment stages, allowing staging new versions before activating them in production when cleared by Quality Assurance (QA)
• Full support of MacOS
• Full revamping of the options for the opentrep-{indexer,dbmgr,searcher} command-line programs, supporting server-side deployments
• Full support of the new OpenTravelData (OPTD) data files, which also reference non-IATA POR (points of reference). Hence, ICAO- and UN/LOCODE-referenced POR may now be indexed

Release 0.06.6

The Python libraries are now installed into standard directory

Release 0.06.5

• The POR (points of reference) data file has been renamed, from ORI to OPTD, the latter standing for Open Travel Data, i.e., the name of the project maintaining that file. The new location is now https://github.com/opentraveldata/opentraveldata/tree/master/opentraveldata and the file is named optd_por_public.csv.
• When only (IATA, ICAO) codes are used in the query string, the POR are retrieved from the underlying database, when existing (and from the classical free-text search when no database is available).
• The US DOT (Department of Transportation) World Area Codes (WAC) have been added to the POR data file, and is now retrieved by OpenTREP.

Release 0.06.1

• The SQL database layer has been re-written.
  • A new program, namely opentrep-dbmgr, can now create, update and query the SQL database, which can be SQLite3 or MySQL/MariaDB.
  • There is still some work to do to use the SQL database when only codes are detected within the search string.
• Issue #6 (http://github.com/trep/opentrep/issues/6):
  • Many POR are also indexed with collateral types. For instance, air bases are also indexed as airports.
• Issue #7 (http://github.com/trep/opentrep/issues/7):
  • The punctuation characters are removed. Note that, as the Unicode normalisation procedure is used, there is still an issue when called from Django (for reasons unknown yet).
• Issues #4 (http://github.com/trep/opentrep/issues/4) and #8 (http://github.com/trep/opentrep/issues/8):
  • Fixed the ORI (former name of OPTD) POR data file (now optd_por_public.csv).

Release 0.06.0

• Issue #1 (http://github.com/trep/opentrep/issues/1): the search algorithm is now modular.
• Issues #3 (#3) and #5 (#5): POR are now indexed with their associated PageRank value (equal to 0.1% when there is no PageRank vallue).
• Latest ORI POR data: http://github.com/opentraveldata/optd/blob/trunk/refdata/ORI/ori_por_public.csv