CityOS2CARTO

Orchestrate CityOS API data downloads, GeoParquet conversion, and CARTO uploads.

Updated Aug 23, 2026

Search Tags:#data pipeline #etl #gis #carto #cityos #urban data

Ready to run

npx skills add https://github.com/danielprats/01_03_VIMEP --skill cityos2carto

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: CityOS2CARTO
Source: https://github.com/danielprats/01_03_VIMEP/tree/main/AssistentIA/_skills/CityOS2CARTO
Command: npx skills add https://github.com/danielprats/01_03_VIMEP --skill cityos2carto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, pandas, geopandas, python-dotenv, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the complex process of transferring urban asset data from the CityOS API to CARTO, ensuring data is up-to-date and accessible for analysis and visualization.

Core Features & Use Cases

End-to-End Data Pipeline: Orchestrates the entire flow from data acquisition to final destination.
Flexible Data Scope: Allows selection of specific data types (maintainments, IRIS, inventories) or a full sync.
Use Case: Automatically update all public lighting maintenance records in CARTO for the previous month, ensuring city planners have the latest information on infrastructure status.

Quick Start

Run the CityOS2CARTO skill to process the data for period 2501.

Frequently Asked Questions about CityOS2CARTO

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I sync urban asset data from CityOS to CARTO automatically?▼

Syncing CityOS data to CARTO requires configuring a GCS bucket and CARTO API keys to automate downloading from the CityOS API, converting to GeoParquet, and uploading to Google Cloud Storage and CARTO for analysis and visualization.

What do I need to configure before transferring CityOS API data to CARTO?▼

Before transferring CityOS API data to CARTO, you must configure a Google Cloud Storage bucket and CARTO API keys. These credentials enable the pipeline to stage data in GeoParquet format before uploading it to the CARTO platform.

Can I select specific data types like IRIS incidents when syncing from CityOS to CARTO?▼

Yes, you can select specific data types like IRIS incidents, maintainments, or various inventories when syncing from CityOS to CARTO. The pipeline allows flexible data scope selection, or you can perform a full sync of all available asset types.

What is the best way to convert CityOS API data to GeoParquet for GIS analysis?▼

The best way to convert CityOS API data to GeoParquet for GIS analysis is using an ETL pipeline built with geopandas and pandas. This approach automates the download, conversion, and upload process to Google Cloud Storage and CARTO.

Why does my CityOS to CARTO data pipeline require Google Cloud Storage?▼

Your CityOS to CARTO data pipeline requires Google Cloud Storage to stage the GeoParquet files generated from the CityOS API download. CARTO integrates with GCS to import and visualize the geospatial data efficiently.

Does this ETL pipeline support syncing public lighting maintenance records to CARTO?▼

Yes, this ETL pipeline supports syncing public lighting maintenance records to CARTO. It can automatically update these records for a specific period, ensuring city planners have the latest infrastructure status information for analysis.