• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • Schema
    • None

      (not sure if the MBS project would be more fitting for this issue)

      The place coordinates in the search response are treated as string:

      $ curl -sL "https://musicbrainz.org/ws/2/place/?query=place:%22royal%20albert%20hall%22%20AND%20address:london&fmt=json" | jq ".places[].coordinates"
      {
        "latitude": "51.50105",
        "longitude": "-0.17748"
      }

      whereas they are treated as float when accessing them through a fetch query:

      $ curl -sL "https://musicbrainz.org/ws/2/place/4352063b-a833-421b-a420-e7fb295dece0?fmt=json" | jq ".coordinates"
      {
        "latitude": 51.50105,
        "longitude": -0.17748
      }

      IMO they should be treated as float when accessing them through a search query too since it seems more fitting and will help maintain consistency between both the search and fetch endpoints.

       

       

          Loading...

            • Icon: Bug Bug
            • Resolution: Unresolved
            • Icon: Normal Normal
            • None
            • None
            • Schema
            • None

              (not sure if the MBS project would be more fitting for this issue)

              The place coordinates in the search response are treated as string:

              $ curl -sL "https://musicbrainz.org/ws/2/place/?query=place:%22royal%20albert%20hall%22%20AND%20address:london&fmt=json" | jq ".places[].coordinates"
              {
                "latitude": "51.50105",
                "longitude": "-0.17748"
              }

              whereas they are treated as float when accessing them through a fetch query:

              $ curl -sL "https://musicbrainz.org/ws/2/place/4352063b-a833-421b-a420-e7fb295dece0?fmt=json" | jq ".coordinates"
              {
                "latitude": 51.50105,
                "longitude": -0.17748
              }

              IMO they should be treated as float when accessing them through a search query too since it seems more fitting and will help maintain consistency between both the search and fetch endpoints.

               

               

                    kartik1712 amCap1712
                    ritiek Ritiek Malhotra
                    Votes:
                    0 Vote for this issue
                    Watchers:
                    1 Start watching this issue

                      Created:
                      Updated:

                        Version Package

                          kartik1712 amCap1712
                          ritiek Ritiek Malhotra
                          Votes:
                          0 Vote for this issue
                          Watchers:
                          1 Start watching this issue

                            Created:
                            Updated:

                              Version Package