Academics: drive citations for your publications by disseminating data under a DOI (Digital Object Identifier), boost your h-index.
Small companies: monetise your existing geospatial data directly, or indirectly by understanding new use cases, customer categories, and offering complementary services.
Large companies: streamline data sharing between business units, improve efficiency, accelerate innovation by intrapreneurs.
Government: disseminate tax-payer funded data back to the tax-paying community, enabling new business growth, academic research, and outreach.
We develop, maintain, monitor, and improve our own highly scalable web API infrastructure; our economy-of-scope results in low up-front costs for you. All development is undertaken in Australia or the UK.
Low
Formula based, test data, no data management.
Example: Longman gravitational equations here.
Estimate: $1000 AUD
Mid
Mixed code Python binding development, some data management.
Example: Aviation radiation at a point here.
Estimate: $5000 AUD
High
Management of large datasets and/or hosting automated data science pipelines.
Example: NEMO oceanic biogeochemistry here.
Estimate: $10000 AUD
Supreme
Costings above for each API build, along with a white-labelled Developer Portal.
Example: Amentum Scientific developer portal here.
Estimate: $50000 AUD
In the process of developing Web APIs, the associated scientific data management automation pipelines, API user management systems, test suites, and CD/CI pipelines, we create light-weight tools that make our lives easier. We give back to the community with these open source projects:
async_api_caller - Making asynchronous web API calls using Python's asyncio can be complicated. This package abstracts away complexity for the common case of needing to make multiple web API calls while varying query parameters.
map_plotter - Abstracts away some complexity of using the Python packages cartopy/matplotib to create global intensity maps of a quantity.
file_unittest - Provides a way to create and run Python unit tests based on text-based files (aka golden testing). The user generates a set of text files (golden files) which are then re-generated and compared whenever the tested code-base changes.
More to follow.