|
|
|
|
|
by msaharia
990 days ago
|
|
Exactly - I can tell you an example from India. India has the Indian Meteorological Department (IMD) precipitation dataset. Even if your estimates are more accurate, no company will use your dataset to design/validate a civil engineering design. This has to do with liability of using a dataset from a "non-official" source. Right now, you are stuck in the middle where it is not viable for non-US companies to use it, while US companies will mostly rely on NOAA Atlas. If this is to become a public-facing product, then the current pricing is too high, and might have to develop an alternative business model. Maybe people are interested in checking the floodplain zonation/xrain before buying a house, for example. But no SAAS in that case. How flexible is your codebase to incorporate regional datasets? I think you will have to regional merging. What are your current costs of running the setup? Any possibility/plans of white-labeling the codebase? |
|