Merge sites into a super layer in Cloudrf Cloud RF
A documented Cloudrf Cloud RF operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Merge sites into a super layer.
- GETReads data · Analyse
api.cloudrf.com/mesh
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Cloudrf Cloud RF operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other Cloudrf Cloud RF operations
- Upload clutter data as GeoJSONPOST · changes data
- Create a point-to-multipoint heatmapPOST · changes data
- Point-to-point path profile analysis (Tx to Rx)POST · changes data
- Point-to-multipoint path profile analysis (Many Tx, one Rx)POST · changes data
- List calculations from your archiveGET · reads data
- Export a calculation in a GIS file formatGET · reads data
- Find the best server for somewhereGET · reads data
- Find the best server for overlapping coverageGET · reads data
Questions
- Can HumDay merge sites into a super layer in Cloudrf Cloud RF?
- Yes. This operation is published in Cloudrf Cloud RF's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my Cloudrf Cloud RF account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Cloudrf Cloud RF.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Cloudrf Cloud RF account.
Where this came from
Read from a published API description for Cloudrf Cloud RF at api.cloudrf.com/swagger-ui/Cloud-RF_API2.0.yaml. The description above is the provider’s own wording, not ours. Last published 2021-07-05.