1. 30 Aug, 2020 1 commit
  2. 23 Jun, 2020 2 commits
  3. 25 Jul, 2019 1 commit
  4. 06 May, 2018 1 commit
  5. 01 Apr, 2018 1 commit
  6. 30 Mar, 2018 1 commit
  7. 01 Mar, 2017 3 commits
  8. 25 Jan, 2017 1 commit
  9. 05 Aug, 2016 2 commits
  10. 04 Aug, 2016 4 commits
  11. 02 Aug, 2016 1 commit
  12. 28 Jul, 2016 1 commit
  13. 17 Jun, 2016 1 commit
  14. 15 Jun, 2016 1 commit
  15. 13 Jun, 2016 1 commit
  16. 08 Jun, 2016 1 commit
  17. 11 Dec, 2015 1 commit
  18. 11 Nov, 2015 1 commit
  19. 04 Sep, 2015 1 commit
  20. 03 Aug, 2015 1 commit
  21. 24 Oct, 2014 3 commits
    • Jörg Richter's avatar
      0.2 Release · 1caf55e6
      Jörg Richter authored
      1caf55e6
    • Jörg Richter's avatar
      Adapt to DM 4.4. · 08bcdc6d
      Jörg Richter authored
      CHANGE in REST API:
      
      The request format has not changed (see README), but the result has: By default the result Geo Coordinate topics do ''not'' include their Longitude and Latitude child topics.
      (The lon/lat values are still available in the Geo Coordinate topic value in space-limited concatenated form.)
      
      If you want include the Geo Coordinate topic's actual Longitude and Latitude child topics in the result append `?include_childs=true` to the request.
      08bcdc6d
    • Jörg Richter's avatar
      Bump version to 0.2-SNAPSHOT. · 14d876d0
      Jörg Richter authored
      Depends on DM 4.4 release.
      14d876d0
  22. 10 Aug, 2014 6 commits
    • Jörg Richter's avatar
      Add example to README · 44875fcb
      Jörg Richter authored
      44875fcb
    • Jörg Richter's avatar
      0.1 Release · 925b6354
      Jörg Richter authored
      925b6354
    • Jörg Richter's avatar
      Fill the geospatial index initially (#633). · 6c9486e5
      Jörg Richter authored
      When the plugin is deployed for the first time the geospatial index is filled with all existing Geo Coordinate topics. So, existing geo data is searchable from the start.
      
      The dm4-geospatial plugin now has reached its first milestone and is about to be released as 0.1
      
      See #633.
      6c9486e5
    • Jörg Richter's avatar
      Fix searching an empty geospatial index (#633). · 0d095524
      Jörg Richter authored
      When an empty geospatial index is searched an empty result is returned. No exception is thrown.
      
      See #633.
      0d095524
    • Jörg Richter's avatar
      Remove entries from geospatial index (#633). · af280fd1
      Jörg Richter authored
      Once a Geo Coordinate topic is deleted (e.g. when an Address is deleted) the corresponding entry is removed from the geospatial index.
      
      NOTE: this module is still experimental. Only use it with a testing DB.
      
      See #633.
      
      -----------------------------------------------------------------------
      
      CORRECT COMMIT MESSAGE FOR PREVIOUS COMMIT:
      
      Update geospatial index (#633).
      
      Once a Geo Coordinate topic changes (e.g. when an Address is changed) the geospatial index is updated accordingly.
      
      See #633.
      af280fd1
    • Jörg Richter's avatar
      Index Geo Coordinate topics directly (#633). · 36fc1fee
      Jörg Richter authored
      The internal indexing approach is changed: the Geo Coordinate topics are indexed directly, so that they become an active part of the R-tree build up by Neo4j Spatial. This supports index update and delete operations more natural.
      
      NOTE: this module is still experimental. Only use it with a testing DB.
      
      See #633.
      36fc1fee
  23. 08 Aug, 2014 1 commit
    • Jörg Richter's avatar
      Index Geo Coordinate topics directly (#633). · d4c917a1
      Jörg Richter authored
      The internal indexing approach is changed: the Geo Coordinate topics are indexed directly, so that they become an active part of the R-tree build up by Neo4j Spatial. This supports index update and delete operations more natural.
      
      NOTE: this module is still experimental. Only use it with a testing DB.
      
      See #633.
      d4c917a1
  24. 07 Aug, 2014 1 commit
    • Jörg Richter's avatar
      First working version (#633). · 52baac35
      Jörg Richter authored
      New API for performing a proximity search.
      
      Geospatial API:
      {{{
      import de.deepamehta.plugins.geomaps.model.GeoCoordinate;
      
      List<Topic> getTopicsWithinDistance(GeoCoordinate geoCoord, double maxDistanceInKm)
      }}}
      
      REST API:
      {{{
      GET /geospatial/<lon>,<lat>/distance/<km>
      }}}
      
      Returned are Geo Coordinate topics (as defined in the Geomaps module).
      
      Each time a Geo Coordinate topic is created or updated its values are automatically indexed by means of Neo4j Spatial (http://www.neo4j.org/develop/spatial). That is typically each time an Address topic is created/updated, e.g. when editing a Person or an Institution.
      
      Existing Geo Coordinate topics are not yet indexed (this remains to be implemented). Only create and update operations are respected at the moment.
      
      There is a bug in Neo4j Spatial: when the above API is used while the geospatial index has no entries yet, a NullPointerException is thrown.
      
      Hint: with a Geo Coordinate topic at hand you can retrieve the corresponding domain topic (e.g. a Person or Institution) by calling the Geomaps service's
          `Topic getDomainTopic(long geoCoordId)`
      
      See #633.
      52baac35
  25. 05 Aug, 2014 1 commit
  26. 04 Aug, 2014 1 commit