maps
Here are 2,094 public repositories matching this topic...
Bug
For the component Marker, the type of value retrieved from onPress={e => console.log(e.nativeEvent)} does not match the documentation NOR the index.d.ts
What is being logged :
{ action: "marker-press", coordinate: { latitude: 0, longitude: 0 }, id: "unknown", target: 77 }
Environment info
React native info output:
Describe the bug
We are using Angular 9,jest@25.0.0, typescript@3.8.3 and latest ol@6.3.1
While running our unit tests following error occurred:
RangeError: Maximum call stack size exceeded
at getTypeOfFuncClassEnumModule (node_modules/typescript/lib/typescript.js:41221:46)
at getTypeOfSymbol (node_modules/typescript/lib/typescript.js:41342:24)
Ref google-map-react/google-map-react#314 (comment) && #524
Example links in DOC.MD are dead.
This happened because they were hosted in webpackbin, who has been deprecated and merged with [codesandbox.io](https://codesand
-
Updated
Jun 10, 2020
Instructions: replace text surrounded by '*' with your case, please delete this line.
How to reproduce?
Explain how we can get this issue, if you created a repo with the issue, please add the link, blank if you are submitting a suggestion or improvement
Extra notes
Explain what you expect, feedback, images or anything you consider necessary
I am using
Following on from mapbox/mapbox-gl-native#16321
We don't need (and shouldn't use) the logging methods defined by MGLNativeNetworkDelegate : implementation and [protocol](https://github.com/mapbox/mapbox-gl-native/blob/9de0bacf
Shared WebGL context
maptalks's version and what browser you use?
v0.43.0, chrome
Issue description
Layers do not share WebGL context, which creates glitches when a map has more than one 3d layer. For example a buildings layer with a 3D line will not hide the line behind the buildings.
In particular, I am implementing a 3D terrain layer but this layer will not hide (behind mountains) any other 3d element
So, I'm eager to contribute to microG. There's just one problem: I've spent the last 10 hours trying to decipher the codebase, and feel like I'm nonethewiser for it. Could you please please PLEASE add some documentation? At least the architecture? I understand that nobody likes writing docs, and I understand that much of the structure is forced upon you by having to copy GPS, but it's critical i
-
Updated
Jun 25, 2020 - Python
-
Updated
Jun 17, 2020 - TypeScript
Good improvements would include:
- Allow a user to add orthophoto, plant health and DEMs at the same time
- Better transparency controls in layers panel
- Allow Z re-ordering of layers
-
Updated
Jun 25, 2020 - JavaScript
WIP in the branch: port-doc-sphinx-breathe
Instructions and dependencies here.
-
Inspiration:
-
Motivation:
- Sphi
-
Updated
May 25, 2020 - JavaScript
'react-autocomplete' (https://github.com/reactjs/react-autocomplete) is no longer maintained and causing warnings
react-dom.development.js:12357 Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
- Move code with side effects to componentDidMount, and set initial state in the constructor.
- R
I have added fence as a new barrier type for the POI layer. This was an easy addition and works great, until I realized that some ways that have type shop are only getting fence information, and not the shop type. See:

None of following GeoJSON functions are covered with tests yet:
geometryToLayercoordsToLatLngcoordsToLatLngslatLngToCoordslatLngsToCoordsasFeatureSample test (for
latLngToCoords):