Skip to content

Latest commit

 

History

History
84 lines (66 loc) · 2.37 KB

README.md

File metadata and controls

84 lines (66 loc) · 2.37 KB

Geoserver

Build status NPM downloads NPM version Node version Dependency status

In-house Geoserver written in Node.JS.

API

Boundary

Intersect

Methods: POST Endpoint: /api/v1/boundary/intersect

Get boundaries that intersect with a given geometry structure. Or in other words return POLYGONS that a given geometry is a part of / inside of.

curl -X POST \
  -H "Content-Type: Application/Json" \
  -d '{"geojson": { "type": "LineString", "coordinates": [[ 5.32907, 60.39826 ], [ 6.41474, 60.62869 ]] }}' \
  "/api/v1/boundary/intersect"

Has the corresponding output of:

{
  "områder": [
    { "_id": "52408144e7926dcf1500004b", "navn": "Stølsheimen, Bergsdalen og Vossefjellene" },
    { "_id": "52408144e7926dcf15000025", "navn": "Byfjellene i Bergen" },
    { "_id": "52408144e7926dcf15000035", "navn": "Nordhordland" }
  ],
  "fylker": [
    "Hordaland"
  ],
  "kommuner": [
    "Samnanger",
    "Vaksdal",
    "Osterøy",
    "Bergen",
    "Voss"
  ]
}

Line

Analyze

Methods: POST Endpoint: /api/v1/line/analyze

Analyze a LineString and return some interesting properties.

curl -X POST \
  -H "Content-Type: Application/Json" \
  -d '{"geojson": { "type": "LineString", "coordinates": [[ 5.32907, 60.39826 ], [ 6.41474, 60.62869 ]] }}' \
  "/api/v1/line/analyze"

Has the corresponding output of:

{
  "length": 64781,
  "geojson": {
    "type": "LineString",
    "coordinates": [[ 5.32907, 60.39826 ], [ 6.41474, 60.62869 ]],
    "properties": {
      "start": { "type": "Point", "coordinates": [ 5.32907, 60.39826 ] },
      "stop": { "type": "Point", "coordinates": [ 6.41474, 60.62869 ] }
    }
  }
}