jmacura

Results 39 issues of jmacura

### What You Are Seeing? ![obrazek](https://user-images.githubusercontent.com/5598693/155897897-2a0d936e-bb19-4d25-a924-3b417591738a.png) I can see the above error when trying to open the details of some packages with a mouse right-click. Oddly, the error does not...

### Steps to reproduce 1. Create map in OCAD 10 2. Open in Mapper 3. Export to OCAD 10 (new file, do not rewrite) 4. Open in OCAD 10 5....

enhancement

### Steps to reproduce 1. set coordinate system to EPSG:5514 (S-JTSK / Krovak EastNorth, the national system of CZ) 2. add raster template to Mapper 3. File->Import->Anything (tested SHP and...

Where is the list of abbreviations used in the standard? The term "UA" is used extensively throughout the text but not explained anywhere... https://html.spec.whatwg.org/commit-snapshots/009a7316ad7f1b69de978101b043b9b29878d975/#table-of-contents

clarification

**Describe the bug** This is an issue of the [API documentation](https://openlayers.org/en/latest/apidoc/). Some classes have properly described _Observable Properties_, like [VectorLayer](https://openlayers.org/en/latest/apidoc/module-ol_layer_Vector-VectorLayer.html). But some others miss this part of documentation, like [VectorSource](https://openlayers.org/en/latest/apidoc/module-ol_source_Vector-VectorSource.html),...

bug

Adding more OSM tags which can be translated into orienteering map symbols. Namely: - natural=peak - leisure=picnic_table - highway=primary_link - highway=secondary_link - highway=tertiary_link - highway=steps - tourism=information (restricted to guidepost,...

# Feature Request **Is your feature request related to a problem? Please describe.** Currently there are many advanced options when adding data from URL or from File, but almost none...

enhancement
question
LayerSources
GUI

Vite + esbuild, see [Getting started with the Angular CLI's new build system](https://angular.io/guide/esbuild), this one might be tricky due to the custom-webpack builder we use The benefit would be much...

performance
build

Use takeUntilDestroyed instead of 'end' https://angular.io/api/core/rxjs-interop/takeUntilDestroyed

refactoring

Use the new control flow syntax which is preferred. Question: Is this even necessary? Or are we OK to mix control-flow syntax with directive-based syntax? see [Built-in control flow](https://angular.io/guide/control_flow)

refactoring