Skip to main content
Adding two links for reference
Source Link
Glorfindel
  • 3.2k
  • 6
  • 26
  • 33

Convert all you strings into actual latitudes and longitudes using some geocoding service.

Store coordinates of locations in a database that supports Geo distance queries (PostGIS, Elastic search)

Read up on how to query using geo relevance.

You might also want to look into Nested SetsNested Sets but if you hierarchy has variable depth you may want to look into a graph database to have proficient queries.

Convert all you strings into actual latitudes and longitudes using some geocoding service.

Store coordinates of locations in a database that supports Geo distance queries (PostGIS, Elastic search)

Read up on how to query using geo relevance.

You might also want to look into Nested Sets but if you hierarchy has variable depth you may want to look into a graph database to have proficient queries.

Convert all you strings into actual latitudes and longitudes using some geocoding service.

Store coordinates of locations in a database that supports Geo distance queries (PostGIS, Elastic search)

Read up on how to query using geo relevance.

You might also want to look into Nested Sets but if you hierarchy has variable depth you may want to look into a graph database to have proficient queries.

Convert all you strings into actual latitudes and longitudes using some geocoding service.

Store coordinates of locations in a database that supports Geo distance queries (PostGIS, Elastic search)

Read up on how to query using geo relevance.

You might also want to look into Nested Sets but if you hierarchy has variable depth you may want to look into a graph database to have proficient queries.

Convert all you strings into actual latitudes and longitudes using some geocoding service.

Store coordinates of locations in a database that supports Geo distance queries (PostGIS, Elastic search)

Read up on how to query using geo relevance.

  • PostGIS KNN
  • ElasticSearch Geodistance

You might also want to look into Nested Sets but if you hierarchy has variable depth you may want to look into a graph database to have proficient queries.

Convert all you strings into actual latitudes and longitudes using some geocoding service.

Store coordinates of locations in a database that supports Geo distance queries (PostGIS, Elastic search)

Read up on how to query using geo relevance.

You might also want to look into Nested Sets but if you hierarchy has variable depth you may want to look into a graph database to have proficient queries.

deleted 24 characters in body
Source Link

Convert all you strings into actual latitudes and longitudes using some geocoding service.

Store coordinates of locations in a database that supports Geo distance queries (PostGIS, Elastic search)

Read up on how to query using geo relevance.

  • PostGIS KNN
  • ElasticSearch Geodistance

You might also want to look into Nested Sets but if you hierarchy gets to crazy and has variable depth to it you may want to look into a graph database to have proficient queries.

Convert all you strings into actual latitudes and longitudes using some geocoding service.

Store coordinates of locations in a database that supports Geo distance queries (PostGIS, Elastic search)

Read up on how to query using geo relevance.

  • PostGIS KNN
  • ElasticSearch Geodistance

You might also want to look into Nested Sets but if you hierarchy gets to crazy and has variable depth to it you may want to look into a graph database to have proficient queries.

Convert all you strings into actual latitudes and longitudes using some geocoding service.

Store coordinates of locations in a database that supports Geo distance queries (PostGIS, Elastic search)

Read up on how to query using geo relevance.

  • PostGIS KNN
  • ElasticSearch Geodistance

You might also want to look into Nested Sets but if you hierarchy has variable depth you may want to look into a graph database to have proficient queries.

Source Link
Loading