Add files via upload

app-pages/images/readme.md

@@ -0,0 +1 @@
+

app-pages/las-header-reader.md

@@ -0,0 +1,19 @@
+---
+layout: default
+---
+
+[**Back to application list**](../)
+
+---
+
+### Reading LAS/LAZ file header
+
+The application extracts information contained in the LAS/LAZ file header. Supported versions of LAS standard: 1.0, 1.1, 1.2, 1.3, 1.4. Extracted header information can be saved in a text file.
+
+![](./images/LASHeaderReader.jpg)
+
+---
+
+[**Download the app**](https://github.com/DenisAntoshkin/Applications/releases/download/LASHeader/LASHeaderReader.zip)
+
+[**Back to application list**](../)

app-pages/ms-statistics.md

@@ -0,0 +1,64 @@
+---
+layout: default
+---
+
+[**Back to application list**](../)
+
+---
+
+### Dgn file statistics (Bentley CONNECT Edition)
+
+The application shows a list of graphic elements of the dgn file and allows user to select and iterate through them.
+
+![](./images/stats.jpg)
+
+Elements are grouped by attributes:
+*  Level
+*  Type
+*  Color
+*  Line weight
+*  Line style
+
+Single click on a column header sorts the rows by that column.
+
+Double click on a column header turns on/off corresponding attribute and rearranges elements in the table.
+
+User can select one or more groups of elements (rows), using Shift and Ctrl if necessary.
+
+![](./images/stats-control.jpg)
+
+1.  Go to first element
+2.  Go to previous element
+3.  Go to element with given number
+4.  Go to next element
+5.  Go to last element
+6.  Select all specified elements
+7.  Update statistics
+8.  Flag for changing the view scale in accordance with the current element (if the flag is turned off, the view scale does not change)
+
+Elements are displayed in the MicroStation view that is currently active. When displaying an element, the view is always set to Top mode. The depth of the view does not change (if the current element is not visible or partially visible, most likely its z-coordinates are outside the clipping planes of the corresponding MicroStation window)
+
+The current element is highlighted. The element highlighting is automatically reset when you select any standard MicroStation tool or when you close the application window.
+
+---
+
+**Application usage:**
+
+1.	Copy file 'stats.dll' to the folder …\MicroStation CONNECT Edition\MicroStation\Mdlapps\
+2.	Enter key-in "mdl load stats" to run the application
+3.	Select desired line(s) in the list and manage elements using toolbar at the top of the application window
+
+To optimize the use of the utility, the following key-ins are provided:
+
+*	"STATS FIRST" - Go to first element
+*	"STATS LAST" - Go to last element
+*	"STATS PREV" - Go to previous element
+*	"STATS NEXT" - Go to next element
+
+After closing the application window, you can reopen it with key-in command "stats"
+
+---
+
+[**Download the app**](https://github.com/DenisAntoshkin/Applications/releases/download/DgnStatistics/stats.zip)
+
+[**Back to application list**](../)

app-pages/polygon-generation.md

@@ -0,0 +1,40 @@
+---
+layout: default
+---
+
+[**Back to application list**](../)
+
+---
+
+### Polygon generation (Bentley CONNECT Edition)
+
+The application creates square orthogonal polygons that completely cover an area object or a corridor of a linear object. For an area object, the coverage area is defined by the object itself and the specified buffer. The coverage area of a linear object is defined by the centerline and width of the corridor. This tool can be useful to automatically create orthomosaic cutting blocks for linear and area objects.
+
+The centerline of a line object can be an element of type Line (non-zero length), LineString, or Complex Chain. The area object must be of type Shape or Complex Shape.
+
+![](./images/orthotiles.jpg)
+
+*  **Offset** - a buffer relative to the original element that defines the coverage area. For a linear element, this parameter defines half the width of the corridor (on the left and right sides of the centerline)
+*  **Tile size** - polygon side size
+
+Before using the tool, the source element must be selected. Polygons are created in the active layer and with active dgn file attributes.
+
+---
+
+**Application usage:**
+
+1.	Copy file 'orthotiles.dll' to the folder …\MicroStation CONNECT Edition\MicroStation\Mdlapps\
+2.	Enter key-in "mdl load orthotiles" to run the application
+3.	Set desired active attributes in the dgn file
+4.	Select source area or line object
+5.	Set desired parameters in the application dialog and click 'Create tiles' button
+
+After closing the application window, you can reopen it with key-in command "orthotiles"
+
+To use the application in another dgn file, you must restart MicroStation.
+
+---
+
+[**Download the app**](https://github.com/DenisAntoshkin/Applications/releases/download/OrthoTiles/orthotiles.zip)
+
+[**Back to application list**](../)

app-pages/raster-position.md

@@ -0,0 +1,33 @@
+---
+layout: default
+---
+
+[**Back to application list**](../)
+
+---
+
+### Raster files georeferencing (Bentley CONNECT Edition)
+
+The application creates [world files](https://en.wikipedia.org/wiki/World_file) for all rasters attached to dgn file in MicroStation Raster manager.
+
+![](./images/rasterposition.jpg)
+
+---
+
+**Application usage:**
+
+1.	Copy file 'rasterposition.dll' to the folder …\MicroStation CONNECT Edition\MicroStation\Mdlapps\
+2.	Enter key-in "mdl load rasterposition" to run the application
+3.	Click 'Ok' in the dialog
+
+World files are created in the same folders in which the rasters are located. World file names correspond to raster names, extension = first + last raster extension character + 'w'. Those. tif -> tfw, jpg -> jgw, etc.
+
+If world files already exist in the folder, they will be overwritten without warning. If there is no attached raster (such files are marked in red in the Raster manager window), it will be ignored.
+
+After closing the application window, you can reopen it with key-in command "rasterposition"
+
+---
+
+[**Download the app**](https://github.com/DenisAntoshkin/Applications/releases/download/RasterPosition/rasterposition.zip)
+
+[**Back to application list**](../)

app-pages/raster-toggle.md

@@ -0,0 +1,37 @@
+---
+layout: default
+---
+
+[**Back to application list**](../)
+
+---
+
+### Raster toggle (Bentley CONNECT Edition)
+
+The application allows to sequentially display georeferenced rasters loaded into MicroStation Raster manager. For example, it can be used to speed up the digitization of base of buildings and other objects on top of orthorectified images for areas with high-rise buildings.
+
+![](./images/rastertoggle.gif)
+
+The application does not have an interface. Its functionality is run by key-ins:
+*	‘RASTERTOGGLE ACTIVEVIEW’ – defines rasters inside the boundaries of the active MicroStation view
+*	‘RASTERTOGGLE CHANGERASTER’ – sequentially displays rasters from the list defined by the first command in the active MicroStation view
+
+For ease of use it is strongly recommended to bind key-in commands to MicroStation function keys.
+
+---
+
+**Application usage:**
+
+1.	Copy file 'rastertoggle.dll' to the folder …\MicroStation CONNECT Edition\MicroStation\Mdlapps\
+2.	Enter key-in "mdl load rastertoggle" to run the application
+3.	Set desired scene in the active MicroStation view (use Top view setting)
+4.	Enter “rastertoggle activeview” key-in (or press the corresponding MicroStation function key) to determine the rasters that fall into the active view
+5.	Sequentally enter “rastertoggle changeraster" key-in (or press the corresponding MicroStation function key) to toggle rasters
+
+To use the application in another dgn file, you must restart MicroStation.
+
+---
+
+[**Download the app**](https://github.com/DenisAntoshkin/Applications/releases/download/RasterToggle/rastertoggle.zip)
+
+[**Back to application list**](../)

app-pages/readme.md

@@ -0,0 +1 @@
+

app-pages/road-width.md

@@ -0,0 +1,41 @@
+---
+layout: default
+---
+
+[**Back to application list**](../)
+
+---
+
+### Width measurement (Bentley CONNECT Edition)
+
+The application measures the distances between two linear elements with a given step. As a result, lines, distance values and stationing labels are created in the dgn file. This tool was created to measure the width of a road.
+
+The source elements must be of type Line (non-zero length), Line String, or Complex Chain. The result is created in the active layer and with the active attributes of the dgn file.
+
+![](./images/roadwidth.jpg)
+
+*	**Step** - stationing step
+*	**Text size** - size of labels (in Master units)
+*	**2d/3d** - distance measurement mode (for two-dimensional lines the result will be the same)
+
+---
+
+**Application usage:**
+
+1.	Copy file 'roadwidth.dll' to the folder …\MicroStation CONNECT Edition\MicroStation\Mdlapps\
+2.	Enter key-in "mdl load roadwidth" to run the application
+3.	Set desired active attributes in the dgn file
+4.	Set desired parameters in the application dialog and click 'Ok' button
+5.	Specify the centerline with the first left mouse click, the edge of the road with the second left mouse click, and then confirm the entry with the third left mouse click anywhere in the view. Right mouse click cancels the last specified element
+
+Distances are measured along lines perpendicular to the centerline (the first element specified)
+
+After closing the application window, you can reopen it with key-in command "roadwidth"
+
+To use the application in another dgn file, you must restart MicroStation.
+
+---
+
+[**Download the app**](https://github.com/DenisAntoshkin/Applications/releases/download/RoadWidth/roadwidth.zip)
+
+[**Back to application list**](../)

app-pages/tms-tiles.md

@@ -0,0 +1,63 @@
+---
+layout: default
+---
+
+[**Back to application list**](../)
+
+---
+
+### Terrain-RGB-Mapbox tile generation
+
+The application converts [ArcInfo ASCII Grid](https://en.wikipedia.org/wiki/Esri_grid) files into PNG (Terrain-RGB) raster tile structure that can be used in web mapping applications ([**Slippy Map**](https://wiki.openstreetmap.org/wiki/Slippy_map)). Tiles contain elevation information encoded into RGB values according to the rules adopted in the [**Mapbox**](https://www.mapbox.com/) project: [**Mapbox Global elevation data**](https://blog.mapbox.com/global-elevation-data-6689f1d0ba65)
+
+Tile cutting and naming correspond to the [**Tile Map Service**](https://en.wikipedia.org/wiki/Tile_Map_Service) notation, i.e. folder name and raster name are taken from the coordinates of its lower left corner in the [**Web Mercator (EPSG:3857)**](https://spatialreference.org/ref/epsg/3857/) projection.
+
+ArcInfo ASCII Grid files must have square cells and center of bottom-left cell as the origin. These ArcInfo ASCII Grid files can be created automatically from LIDAR data using **TerraScan**.
+
+ASCII file header example:
+
+|:-----------------------|
+|_ncols 546_             |
+|_nrows 790_             |
+|_xllcenter 325484.750_  |
+|_yllcenter 6818819.750_ |
+|_cellsize 0.5000_       |
+|_nodata_value -9999_    |
+
+As a result, in the output folder data structure is created corresponding to the selected resolution levels (zoom) and the area covered by the ArcInfo ASCII Grid source files: **\zoom\x\y.png**
+
+![](./images/tms-tiles.jpg)
+
+**_Raster parameters_**
+*	**Elevation shift** - "zero height". Pixels corresponding to this height will have RGB values = (0, 0, 0)
+*	**Z resolution** - accuracy of height values. It is taken into account	when encoding into color
+
+**_TMS parameters_**
+*	**ASCII folder** - folder containing ArcInfo ASCII Grid source files. Files must have the extension “xyz” - other files are ignored. If the file format with the extension “xyz” does not match the specification, this file will also be ignored during processing
+*	**Raster folder** - target folder in which the result will be saved
+*	**Zoom levels** - minimum and maximum levels of detail (resolution). Information about this parameter can be found [**here**](https://wiki.openstreetmap.org/wiki/Zoom_levels)
+
+**_Coordinate system_**
+*	**Select** - selecting coordinate system of the source ASCII files:
+
+![](./images/crs-selection.jpg)
+
+- The following coordinate systems of ASCII source files are supported:
+  - UTM on WGS84 ellipsoid
+  - custom CS based on the Gauss-Kruger projection
+
+*	**Create** - creating and editing user-defined custom coordinate systems:
+
+![](./images/crs-custom.jpg)
+
+![](./images/crs-definition.jpg)
+
+Parameters in the dialog to define custom coordinate system involve the 7-parameter Helmert transformation **Coordinate frame rotation** and **Datum shift from WGS84**. (When using the **Datum shift to WGS84** and/or **Position Vector Rotation** conversion options, the signs must be changed accordingly.) User-defined custom coordinate systems are saved in the xml-file located in the same folder as the application.
+
+While the application is running, the progress bar at the bottom of the application window shows the progress, total number and number of tiles currently generated.
+
+---
+
+[**Download the app**](https://github.com/DenisAntoshkin/Applications/releases/download/TMSTiles/TMS-tiles.zip)
+
+[**Back to application list**](../)

app-pages/trm-rasters.md

@@ -0,0 +1,40 @@
+---
+layout: default
+---
+
+[**Back to application list**](../)
+
+---
+
+### Terrain-RGB-Mapbox raster generation
+
+The application converts [ArcInfo ASCII Grid](https://en.wikipedia.org/wiki/Esri_grid) files into TIFF files (Terrain-RGB), which contain elevation information encoded into RGB values according to the rules adopted in the [**Mapbox**](https://www.mapbox.com/) project: [**Mapbox Global elevation data**](https://blog.mapbox.com/global-elevation-data-6689f1d0ba65)
+
+The height value for each pixel in the image can be taken using the formula: **H = Elevation shift + (R * 256 * 256 + G * 256 + B) * Z resolution**
+
+Raster georeferencing is saved in *.tfw world files, which are also generated in the output folder.
+
+ArcInfo ASCII Grid files must have square cells and center of bottom-left cell as the origin. These ArcInfo ASCII Grid files can be created automatically from LIDAR data using **TerraScan**.
+
+ASCII file header example:
+
+|:-----------------------|
+|_ncols 546_             |
+|_nrows 790_             |
+|_xllcenter 325484.750_  |
+|_yllcenter 6818819.750_ |
+|_cellsize 0.5000_       |
+|_nodata_value -9999_    |
+
+![](./images/Terrain-RGB.jpg)
+
+*	**ASCII folder** - folder containing ArcInfo ASCII Grid source files. Files must have the extension “xyz” - other files are ignored. If the file format with the extension “xyz” does not match the specification, this file will also be ignored during processing
+*	**TIFF folder** - target folder in which the result will be saved (*.tif + *.tfw). The names of the output files will correspond to the names of the source ones. If the names match, the files in the output folder are overwritten without warning
+*	**Elevation shift** - "zero height". Pixels corresponding to this height will have RGB values = (0, 0, 0)
+*	**Z resolution** - accuracy of height values. It is taken into account	when encoding into color
+
+---
+
+[**Download the app**](https://github.com/DenisAntoshkin/Applications/releases/download/TerrainRGB/TerrainRGB.zip)
+
+[**Back to application list**](../)

app-pages/visionmap-terraphoto.md

@@ -0,0 +1,19 @@
+---
+layout: default
+---
+
+[**Back to application list**](../)
+
+---
+
+### VisionMap A3 -> TerraPhoto
+
+The application converts VisionMap A3 camera data ('Detailed Report.txt') to TerraPhoto data (.iml, .cal). 'Detailed Report.txt' is generated by VisionMap software and contains internal camera parameters and exterior orientation of images. As a result of running the application, TerraPhoto camera files (.cal) and image list (.iml) are created in the folder where the source 'Detailed Report.txt' is located. Exterior orientation of images in the .iml file is calculated in appropriate WGS84 UTM zone.
+
+![](./images/vm2tp.jpg)
+
+---
+
+[**Download the app**](https://github.com/DenisAntoshkin/Applications/releases/download/VM2TP/VM_to_TerraPhoto.zip)
+
+[**Back to application list**](../)