-
Notifications
You must be signed in to change notification settings - Fork 8
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #45 from openkfw/41-change-categories-on-the-left-…
…side-of-the-main-page-project-location-model Split the main
- Loading branch information
Showing
6 changed files
with
163 additions
and
156 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
--- | ||
comments: true | ||
--- | ||
|
||
# FAQs | ||
## Who can be contacted if I need help? | ||
For organizational and project-specific questions, please contact your KfW project counterpart. For technical questions and questions regarding more general aspects of the project location data collection model, we encourage you to create an account on GitHub and get in touch with us by creating an issue in our GitHub repository. We also appreciate your feedback and contributions via GitHub to help us improve our work! | ||
|
||
## Can I also use other geospatial formats rather than KML? | ||
We use Google Earth Pro to verify project location data submitted to our teams which works best with KML. If you are not able to provide data in KML, you might also use GPKG or GEOJSON. We encourage you not to use the Shapefile format since the world has suffered enough from it ;) . | ||
|
||
## My KML file is too large to be sent via email. How can I send it to you? | ||
In this case you should ask your KfW project counterpart. They might provide you with a fileshare (idgard) or you might be able to use your own system of choice. |
Oops, something went wrong.