Open APIs

 View Only
Expand all | Collapse all

TMF673 - GeographicAddress (pre-prod 4.0) - area, street, streetsegment objects missing

  • 1.  TMF673 - GeographicAddress (pre-prod 4.0) - area, street, streetsegment objects missing

    Posted Jul 13, 2020 06:15
    Hi TMF Community,

    Regarding the TMF 673 Geographic Address Management, I realize that in the latest version (pre-production 4.0) that the "Area", "Street" and "StreetSegment" objects are missing:

    Here the swagger of the current version where you can see these objects :



    Like mentionned in the specifications of the current version :

    LIST AREAS
    GET /area?fields=...&{filtering}&.fuzzy={true/false}
    Description
    This operation is the first step of an address completion process, allowing retrieving geographic areas:
    - Step 1: I look for a geographic area (city, locality, district, etc.) using its name
    - Step 2: I look for the streets inside this geographic area
    - Step 3: I get all the street segments (numbers) existing in the street​


    Without these objects, how can we handle the searching of a geographic area ?

    Thanks in advance for your help.



    ------------------------------
    Fethi Ben Bagdad
    VOO SA
    ------------------------------


  • 2.  RE: TMF673 - GeographicAddress (pre-prod 4.0) - area, street, streetsegment objects missing

    TM Forum Member
    Posted Jul 14, 2020 06:23
    Hi Fethi,

    While upgrading GeographicAddress API to v4 we decided to not describe any frontend behavior, like address completion process, which is more a topic of user experience than of systems of records. That's why the endpoints for area, street, street segments have been omitted. If you need other search mechanisms as the GET filtering on the geographicAddress endpoint you're welcome to add them in your own implementation.

    Regards

    Alexis

    ------------------------------
    Alexis de Peufeilhoux
    Deutsche Telekom AG
    ------------------------------