Archive 1.x:Geo-enabling OSF Web Service

Introduction
Geo-enabling a OSF Web Service instance means that different web service endpoint will behave differently if geographic related information is being indexed into the system.

For example, if you geo-enable your OSF Web Service instance, the CRUD: Create and CRUD: Update web service endpoints will take a special care of geo-related information for indexation purposes. Then, a geo-enabled Search web service endpoint will be able to filter searches according to some geo positions.

Configuration
To geo-enable a OSF Web Service instance you have to do the following steps:


 * 1) The Solr server instance has to use the Solr Spatial Query fix. We would suggest you to read this introduction article for good background information about this topic: Location-aware search with Apache Lucene and Solr
 * 2) The Solr instance has to use the   schema
 * 3) The network.ini configuration file specify that the OSF Web Service instance is geo-enabled by specifying   in the   section

Geo-enabled Records
Once you have a geo-enabled OSF Web Service instance, you have to describes (at least some of) your records using geo-related information such as latitude, longitude, polygon coordinates and polylines coordinates.

Also read that other zWiki page that tells you how to geo-enabled a record description: Geo-enabling Datasets