--- title: what asset location data actually is canonical_url: https://ensurance.app/guide/what-asset-location-data-actually-is markdown_url: https://ensurance.app/guide/what-asset-location-data-actually-is.md subtitle: "a headquarters is not the plant, and a sector is not the basin" category: nature-finance --- # what asset location data actually is *a headquarters is not the plant, and a sector is not the basin* Two food plants share a sector and do not share a basin. One stands well back from the channel, on ground the last mapped flood did not reach. The other stands where a river already leaves its banks in an ordinary wet week. Same crop, same quarter, different flood position. A headquarters city will not separate them. A sector code will not either. **Asset location data** is the file that can. It names the facility and places a coordinate, or a parcel, on the ground the facility occupies. The floodplain at the fence, and the upstream system the intake depends on, are the next questions. The file may not have joined either. :::johnson **the file finds the place. it does not hold the place.** The living system was already there. A coordinate can point to a watershed, a forest, or a floodplain. It does not fund it. ::: ## what asset location data is Asset location data is the site record for a real operation: a plant, a mill, a warehouse, a farm, a mine, a port. The row carries the facility, a coordinate or a parcel, and the living system at the fence: the basin, the floodplain, the upstream forest, or the wetland that stores the rise. | record | what it answers | what it leaves open | | --- | --- | --- | | Country or region | Where the parent may operate | Which valley holds the plant | | Headquarters | Where the mail and the board go | Which facility floods | | Sector code | What the industry depends on in general | Which basin is stressed | | Asset location data | Which facility, and which living system | Who funds that living system | A stack of latitudes can still miss the site. A dot on the building where the contracts are signed locates the wrong building. Ask which facility, and which watershed, forest, or floodplain it depends on. ## a headquarters is not the plant Registered offices cluster in cities that do not drain the valleys where food is packed or milled. A headquarters screen can be a fair first pass for a large book. Take it as the only asset location and every plant inherits that city's flood, heat, and distance to the coast. The plants stayed in the valleys. The pin moved to the skyline. One parent can run the plant set back from the channel and the plant whose access road already floods. Fold both into the headquarters and each site inherits the city's flood map or the city's calm. Name the facility, then the river, forest, or floodplain it depends on. If the answer is the city on the letterhead, the file is a headquarters with a map attached. Asset location data starts when the two plants are two places. ## a sector is not the basin Keep the plants unnamed. Both handle a similar crop. Both sit in one sector. One watershed still holds summer water, and a dry month does not stop the line. The other river floods the road, the wells, or the outfall. The split is the basin. A sector heatmap is the coarse end of that ladder. It can say that food processing depends on water, soil, and pollination, and it stops before these two sites diverge. A sector is a class. A basin is a place. Pinning the sector's water need to a coordinate records a type of dependency at a site. Naming the watershed, wetland, or reach that delivers the water, and who depends on it, is the further step in [the missing object is the graph](https://ensurance.app/guide/the-missing-object-is-the-graph?from=guide). One borrower can hold both rows. Averaging them only attaches coordinates to a sector figure. The plants remain different. ## flood turns on a short distance. wind often does not Flood can change a short distance from a river. The bank, the first terrace, and the ground above the last water on the parcel are different exposures, even when they share a gate. A pin from a town name, or from a mailing address that lands on the office, puts both buildings in the same flood. For flood, asset location data has to show which side of the river road the plant is on, and how the floodplain crosses the parcel. A few hundred meters is a wet yard or a lost shift. Wind often does not need that precision. A hurricane or a frontal storm loads roofs across a district. Moving the pin across an industrial park rarely changes the wind a model should use. A heat day that covers a valley works the same way: the site is in it, or the region is. River flood needs the short distance off the channel. Wind needs the facility inside the storm path. A headquarters coordinate does neither of those jobs, and one precision for every peril sorts the two plants back into a single bucket. ## the living system is not inside the file A watershed, a forest, or a floodplain exists whether or not a vendor has its coordinates. The stressed plant's river left its banks before anyone sold a location file. The secure plant's upstream storage was holding water before a sector code met a basin outline. Asset location data finds that living system. The file is not the river, the stand, or the floodplain. The file finds the place. It does not hold the place. [Ensurance](https://ensurance.app/?from=guide) funds that place. We use this kind of location inside underwriting a place, and we do not sell the file, an API, or a measurement seat. ## what to check in the file you have 1. One point for the whole company is the registered office, not the plants. 2. The two plants share a sector and sit in different basins. If the file cannot show that split, it never left the parent. 3. For flood, a short move away from the river should be able to change the result. 4. For wind, that same move usually leaves the answer unchanged. The facility point is enough. ## what the pin is for A desk that already pays for asset location data may already have the two plants as two rows. One sits off the flood. The other gives the road to high water. The file has done its job when that split is visible. The file does not fund the floodplain that keeps the lower plant's road above the rise, or the watershed that plant still depends on upstream. A capital provider, a company with the plants in its supply base, or an insurer carrying the plants can see the site and still hold nothing there. The hold is the natural asset the file already named. The work is protection of that watershed, forest, or floodplain. The unit is the place, counted once, not a seat and not an API call. [Capital providers](https://ensurance.app/solutions/capital-providers?from=guide&topic=location-data) separate acquisition capital on the place from yield paid by the parties who need the place to keep working. If the two plants are already in your book, bring the basins. [Start from the sites and the living systems under them](https://ensurance.app/contact?from=guide&topic=location-data). ## frequently asked questions ### what does asset location data contain? A facility row: a name, and a coordinate or a parcel. It can sit next to a flood map or a watershed boundary. It does not fund the watershed, the forest, or the floodplain. That living system was already there. ## the series - [what asset location data actually is](/guide/what-asset-location-data-actually-is?from=guide) - [who sells nature and climate location data](/guide/who-sells-nature-location-data?from=guide) - [what earth observation data shows](/guide/what-earth-observation-data-shows?from=guide) - [the place keeps the record](/guide/the-place-keeps-the-record?from=guide) - [hold the place the file already found](/guide/hold-the-place-the-file-already-found?from=guide)