## Tasks * [ ] Add more commands that each do only one thing, e.g. `data-source:list`, `data-source:ping`, `data-source:import`, … * [ ] Use (real) logging rather than just printing with Symfony IO stuff when importing data. * [ ] Add a (Data)SourceManager to manage data sources * [ ] Establish naming conventions in codebase * [ ] Mint ADR formulations * [ ] Officially adopt ADRs in team * [ ] Use real config to defined data sources (do we already do this?) * [ ] Pass a `DataSource` to `DataSourceImporter::import(…)` * [ ] What is a "Catalog"? It's a “source manager” * [ ] ~Can a “Service Locator” (<https://symfony.com/doc/current/service_container/subscribers_locators.html#injecting-a-service-locator>) help us managing data sources?~ # Further questions GeoJson * [New Features and Changes in NGSI-LD v1.3.1](https://docbox.etsi.org/ISG/CIM/Open/NGSI-LD_API_v1.3.1-New_Features_and_Changes.pdf) * https://github.com/ScorpioBroker/ScorpioBroker/issues/128 * https://github.com/ScorpioBroker/ScorpioBroker/issues/576 * <https://fiware-datamodels.readthedocs.io/en/stable/guidelines/index.html#modelling-location> Is a `location` property the way to store location data on an entity? <https://fiware-datamodels.readthedocs.io/en/stable/ngsi-ld_howto/>
Tasks
data-source:list,data-source:ping,data-source:import, …DataSourcetoDataSourceImporter::import(…)Can a “Service Locator” (https://symfony.com/doc/current/service_container/subscribers_locators.html#injecting-a-service-locator) help us managing data sources?Further questions
GeoJson
Is a
locationproperty the way to store location data on an entity? https://fiware-datamodels.readthedocs.io/en/stable/ngsi-ld_howto/