Known issues and limitations

Continue reading to view the current known issues of the AgStack project. There is also a link to the Jira issue if you are interested in helping to resolve the issue.

Documentation known issues

Real URLs for API documentation are inaccurate

  • When you select Asset registry from the APIs drop-down tab, the User registry API is displayed with the following URL:

    https://agstack.github.io/agstack-website/asset_registry_api.

  • When you select Asset registry from the Select a definition drop-down menu, the Asset registry API is displayed with the following URL:

    https://agstack.github.io/agstack-website/user_registry_api?urls.primaryName=Asset%20registry

  • Similarly, when you select User registry from the Select a definition drop-down menu, the URL is not updated accurately. This is due to the Swagger configuration for selecting definitions. To view the API that you want from the Swagger user interface, you must select the API from the Select a definition drop-down menu.

Documentation Jira issues

  • AG-23 - Ensure there are effective and helpful READMES for the AgStack repos

Asset registry known issues

Field boundary management unavailable

  • Updating or deleting field boundaries is not supported.

Field registeration limits

  • You can only create GeoIDs for fields less than 1000 acres. For example, forests for hydrology, political boundaries, etc. registration is not supported.

Return to the AgStack Home page.