-
Notifications
You must be signed in to change notification settings - Fork 11
How to Expose Data Via Feature Services
James Kerr edited this page Apr 3, 2019
·
2 revisions
After installing the connector, the following describes the basic steps required to expose your data as features via a feature service:
- Load the data that you want into MarkLogic – This could be done via a DHF-based application or as a standalone dataset (not a data integration use case)
- GeoJSON is the easiest to deal with
- MarkLogic supports other formats as well: https://docs.marklogic.com/guide/search-dev/geospatial#id_77391
- Determine what the “features” are in the documents – I.E. if you have a bunch of flight data about airplane locations, the features are likely the airplanes
- Create TDE templates to extract the properties from the documents that you want to have in the features – I.E. for flight data, maybe the airplane tail number, airline, etc.
- Create a service descriptor for the feature service you want to expose
- Define the service name
- Configure the layers you want the service to serve – Each layer has the following
- number (starts at 0)
- name
- extents
- data source configuration (what schema and view to use), and bounding query (an option MarkLogic query that limits what documents to pull features from)
- Here’s an example of a service descriptor: https://github.com/koopjs/koop-provider-marklogic/blob/master/config/example/services/GDeltExample.json
- Load the service descriptor to the database