Skip to content

Commit

Permalink
Automated wiki-website update
Browse files Browse the repository at this point in the history
  • Loading branch information
opensha-website-robot committed May 15, 2024
1 parent 1e49bdd commit b40bfff
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions Geospatial-File-Formats.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ At a minimum, a GeoJSON fault must contain the **3 following items**:
#### 1. Fault Trace
_[(return to top)](#table-of-contents)_

The fault trace must be present in the `geometry` object in the form of a `LineString` or `MultiLineString`. If a `MultiLineString` is encountered and it contains a single `LineString` (GIS softwares may output single lines in this format), it is supported. If a `MultiLineString` is encountered and it contains two `LineString`s, then the second trace is treated as a lower trace; that lower trace must be below the upper trace (it must explicitly specify depths in the coordinate array), and must be in the same general direction as the upper trace.
The fault trace must be present in the `geometry` object in the form of a `LineString` or `MultiLineString`. If a `MultiLineString` is encountered and it contains a single `LineString` (GIS softwares may output single lines in this format), it is supported. If a `MultiLineString` is encountered and it contains two `LineString`s, then the second trace is treated as a lower trace; that lower trace must be below the upper trace (it must explicitly specify depths in the `coordinates` array), and must be in the same general direction as the upper trace.

Example fault trace as a `LineString` with 2 points:

Expand All @@ -43,7 +43,7 @@ Example fault trace as a `LineString` with 2 points:
}
```

Example upper and lower fault trace as a `MultiLineString`:
Example upper and lower fault traces as a `MultiLineString`, each with explicitly stated depths in the `coordinates` array:

```json
"geometry": {
Expand Down

0 comments on commit b40bfff

Please sign in to comment.