POST Closest Point No Longer Working?

[SeaDude]

Creating an issue

We prefer that you create documentation feedback issues using the Feedback link on the published article - the feedback control on the doc page creates an issue that contains all the article details so you can focus on the feedback part.

• I don't see a "Give Feedback" area in the POST Closest Point docs page.

You can also create a feedback issue here in the repo. If you do this, please make sure your issue lists:

• [x] The relevant Azure service or technology.
  • Azure Maps API: POST Closest Point
• [X] A link to the published documentation article that you have feedback about.
  • Link to Example
• [X] Clear, specific feedback that the author can act on.
  • The Example POST body no longer works.
  • Steps to reproduce:
  • Click "Try It"
  • format : json
  • api-version : 1
  • lat : 47
  • lon : -122
  • subscription-key : <my Azure Maps API key>
  • Header: Content-Type : application/json
  • Request Body: (straight from the example)

    {
    "FeatureCollection": {
    "type": "FeatureCollection",
    "features": [
    {
    "type": "Feature",
    "properties": {
      "geometryId": 1001
    },
    "geometry": {
      "type": "Point",
      "coordinates": [
        -105.02860293715861,
        40.516153406773952
      ]
    }
    },
    {
    "type": "Feature",
    "properties": {
      "geometryId": 1002
    },
    "geometry": {
      "type": "Point",
      "coordinates": [
        -105.02860381672178,
        40.515990990037309
      ]
    }
    },
    {
    "type": "Feature",
    "properties": {
      "geometryId": 1003
    },
    "geometry": {
      "type": "Point",
      "coordinates": [
        -105.02812292879467,
        40.516058678088562
      ]
    }
    }
    ]
    }
    }

  • Results:

Response Code: 400
Headers
HTTP

Copy
content-length: 428
content-type: application/json; charset=utf-8
date: Mon, 01 Jul 2019 22:21:44 GMT
strict-transport-security: max-age=31536000; includeSubDomains
x-content-type-options: nosniff
x-correlation-id: fc81cd35-a61d-470a-99e1-f3217a6320ec
x-ms-azuremaps-region: West US 2
Body
{
  "error": {
    "code": "UserData",
    "message": "The property 'type' MUST be defined with a valid value of either point, linestring, polygon, multipoint, multilinestring, multipolygon, geometrycollection, feature, featurecollection.; The value '' is not valid for the property 'type'. The valid GeoJSON types include point, linestring, polygon, multipoint, multilinestring, multipolygon, geometrycollection, feature, featurecollection."
  }
}

My production runs which are based on this example no longer work either. Has something changed?

Thank you

[mikeurnun]

Hi @SeaDude Thank you for your feedback! Since this is a channel for driving improvements towards MS Docs, could you reference the URL of a specific documentation that you were following? That way, we're able to connect you with the right team that can assist you better :)

[SeaDude]

Hi there @mike-urnun-msft , its right there in the OP. Second check box "Link to Example".

[SeaDude]

After troubleshooting a while, I believe I figured out the issue:

• The documentation should NOT have...

{
  "FeatureCollection": 

... on the front end of the POST body.

The final } should also be removed to produce valid JSON.

[SeaDude]

I want a pony and a raise

[SeaDude]

PS. Here is a geojson linter to help out in the future: http://geojsonlint.com/

[SeaDude]

PPS, I had Microsoft Flows running based on the Azure Maps Docs so either:

1. The API Schema changed and the docs didn't keep up OR
2. The docs changed Since there is no edit date on the docs, I can't tell which is which.