geodata with only apiUrl for already existing path

[bariela]

Description

Removed condition for collectionName in geodata config, so the geodata can be defined by "apiUrl" to already existing collection and data by just url

Motivation and Context

Came across usecase, where I've got existing db collection

How has this been tested?

Screenshots (if appropriate):

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• [ ] I have read the CONTRIBUTING document.
• [ ] I have checked to ensure that there aren't other open Pull Requests for the same update/change.
• [ ] My code follows the code style of this project.
• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.
• [ ] I have added tests to cover my changes.
• [ ] All new and existing tests passed.

[srezacova]

https://github.com/openkfw/Oscar/blob/e646b217598dd01e08c823edf38aad7fb46f5d41/initial-data-load/src/mapLayers/layersGeoDataUpload.ts#L81 Hi, is it necessary to have this line here now? If data.apiUrl exist, we have already set it. If not, undefined will be returned even without this line.

[bariela]

https://github.com/openkfw/Oscar/blob/e646b217598dd01e08c823edf38aad7fb46f5d41/initial-data-load/src/mapLayers/layersGeoDataUpload.ts#L81

Hi, is it necessary to have this line here now? If data.apiUrl exist, we have already set it. If not, undefined will be returned even without this line.

true, good catch!