As a developer, you can see GEODI in two parts: the engine and user interfaces. The engine provides all core functionality and has a REST API for all of it.
The user interfaces created with HTML/CSS/Javascript rely on GEODI REST API. So, whenever you wonder how a function uses GEODI, press F12 and inspect the HTML.
Some parts of the UI can also be used as iframes. Thus, you may directly use a map, query result, or viewer in your code and save days, maybe months. You will control the look and feel.
The API documentation is divided into two parts. This site has many pages of detailed documentation on basic API. Please walk around these pages to get a basic idea of them. You will see sample applications in different languages and even embedded forms to experience some calls directly.
The second part is GEODI itself. <geodiurl>/API URL opens a developer page and lists the methods, parameters, and access to basic things like token creation.
The last is the FAQ part. We have gathered as many questions as we have had so far and tried to give answers. We strongly suggest you read the FAQ before digging deeper into your software.
The Support Q has API knowledge, so she may answer some of your questions but not write a code for you. 
Good luck on your coding journey, and we wish you the best quality codes.
| Child pages (Children Display) |
|---|