Load Longdo Map data in Python using dltHub
Build a Longdo Map-to-database or-dataframe pipeline in Python using dlt with automatic Cursor support.
In this guide, we'll set up a complete Longdo Map data pipeline from API credentials to your first data load in just 10 minutes. You'll end up with a fully declarative Python pipeline based on dlt's REST API connector, like in the partial example code below:
Example code
Why use dltHub Workspace with LLM Context to generate Python pipelines?
- Accelerate pipeline development with AI-native context
- Debug pipelines, validate schemas and data with the integrated Pipeline Dashboard
- Build Python notebooks for end users of your data
- Low maintenance thanks to Schema evolution with type inference, resilience and self documenting REST API connectors. A shallow learning curve makes the pipeline easy to extend by any team member
- dlt is the tool of choice for Pythonic Iceberg Lakehouses, bringing mature data loading to pythonic Iceberg with or without catalogs
What you’ll do
We’ll show you how to generate a readable and easily maintainable Python script that fetches data from longdo_map’s API and loads it into Iceberg, DataFrames, files, or a database of your choice. Here are some of the endpoints you can load:
-
Route Service: Endpoints related to route guidance, traffic speed, pathfinding, and snapping routes to the nearest road.
/RouteService/json/route/guide: Provides route guidance based on start and end coordinates./RouteService/json/traffic/speed: Retrieves traffic speed information at a specific location./RouteService/json/route/path: Returns the path for a given route ID./RouteService/json/route/snap: Snap a given route to the nearest road./RouteService/json/route/matrix: Calculates travel times or distances between multiple points.
-
POI Service: Endpoints for points of interest, including searching and geocoding addresses.
/POIService/json/address: Retrieves address information based on geocode./POIService/json/search: Searches for points of interest based on latitude and longitude.
-
Geo Service: Provides geographic information related to specified areas.
/GeoServiceMS/json/areainfo: Returns information about a specified area defined by a polygon.
-
Map Services: General endpoints for accessing map-related services.
/map/services/address: Accesses address-related services./map/services/addresses: Retrieves a list of addresses.
You will then debug the Longdo Map pipeline using our Pipeline Dashboard tool to ensure it is copying the data correctly, before building a Notebook to explore your data and build reports.
Setup & steps to follow
💡Before getting started, let's make sure Cursor is set up correctly:
- We suggest using a model like Claude 3.7 Sonnet or better
- Index the REST API Source tutorial: https://dlthub.com/docs/dlt-ecosystem/verified-sources/rest_api/ and add it to context as @dlt rest api
- Read our full steps on setting up Cursor
Now you're ready to get started!
-
⚙️ Set up
dltWorkspaceInstall dlt with duckdb support:
pip install "dlt[workspace]"Initialize a dlt pipeline with Longdo Map support.
dlt init dlthub:longdo_map duckdbThe
initcommand will setup the necessary files and folders for the next step. -
🤠 Start LLM-assisted coding
Here’s a prompt to get you started:
PromptPlease generate a REST API Source for Longdo Map API, as specified in @longdo_map-docs.yaml Start with endpoints matrix and path and skip incremental loading for now. Place the code in longdo_map_pipeline.py and name the pipeline longdo_map_pipeline. If the file exists, use it as a starting point. Do not add or modify any other files. Use @dlt rest api as a tutorial. After adding the endpoints, allow the user to run the pipeline with python longdo_map_pipeline.py and await further instructions. -
🔒 Set up credentials
To use the Longdo Map API, you need a Longdo Map API Key, which should be included in your requests, and for some endpoints, a JSONP Callback function can be specified for the response format.
To get the appropriate API keys, please visit the original source at https://api.longdo.com/map/doc/ref.php. If you want to protect your environment secrets in a production environment, look into setting up credentials with dlt.
-
🏃♀️ Run the pipeline in the Python terminal in Cursor
python longdo_map_pipeline.pyIf your pipeline runs correctly, you’ll see something like the following:
Pipeline longdo_map load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset longdo_map_data The duckdb destination used duckdb:/longdo_map.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs -
📈 Debug your pipeline and data with the Pipeline Dashboard
Now that you have a running pipeline, you need to make sure it’s correct, so you do not introduce silent failures like misconfigured pagination or incremental loading errors. By launching the dlt Workspace Pipeline Dashboard, you can see various information about the pipeline to enable you to test it. Here you can see:
- Pipeline overview: State, load metrics
- Data’s schema: tables, columns, types, hints
- You can query the data itself
dlt pipeline longdo_map_pipeline show -
🐍 Build a Notebook with data explorations and reports
With the pipeline and data partially validated, you can continue with custom data explorations and reports. To get started, paste the snippet below into a new marimo Notebook and ask your LLM to go from there. Jupyter Notebooks and regular Python scripts are supported as well.
import dlt data = dlt.pipeline("longdo_map_pipeline").dataset() # get "matrix" table as Pandas frame data."matrix".df().head()