Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/amsterdam/amsterdam-react-maps
Examples of map implementations (react-maps + ASC)
https://github.com/amsterdam/amsterdam-react-maps
leaflet react styled-components team-opdrachten typescript
Last synced: 3 months ago
JSON representation
Examples of map implementations (react-maps + ASC)
- Host: GitHub
- URL: https://github.com/amsterdam/amsterdam-react-maps
- Owner: Amsterdam
- License: mpl-2.0
- Created: 2019-12-24T09:29:27.000Z (about 5 years ago)
- Default Branch: master
- Last Pushed: 2024-04-15T12:35:24.000Z (10 months ago)
- Last Synced: 2024-11-09T16:48:56.194Z (3 months ago)
- Topics: leaflet, react, styled-components, team-opdrachten, typescript
- Language: TypeScript
- Homepage: https://amsterdam.github.io/amsterdam-react-maps/?path=/story/introduction-welcome--page
- Size: 118 MB
- Stars: 10
- Watchers: 13
- Forks: 2
- Open Issues: 16
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: docs/CONTRIBUTING.md
- License: LICENSE
- Code of conduct: docs/CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
# Amsterdam React Maps (ARM)
[](https://github.com/storybooks/storybook)
[](https://github.com/ellerbrock/typescript-badges/)
[](https://github.com/prettier/prettier)
[](https://github.com/styled-components/styled-components)
A repo with components / utilities to be used in projects published by [Amsterdam](https://github.com/Amsterdam).
It also contains an "stories" directory where we put so-called "recipes" that developers at Amsterdam can basically copy/paste in their own projects
[This is the link to the story book demo site with examples](https://amsterdam.github.io/amsterdam-react-maps)
## Motivation
Currently we have a few applications that use leaflet with own developed components. The problem with this approach is that it's unable to share certain components / logic.
Because we know we cannot create a one-size-fits-all leaflet application, we decided to create this repo that serves two responsibilities:
1. Inspecting examples of implementations, so these can simply be copied to the user's project
2. Providing compound-components / utilities / configurations for amsterdam-specific projects, so these can be maintained on one place: this repo.
## Structure
This project is a monorepo with 3 packages
- [arm-core](packages/arm-core) - core things like Map, BaseLayer, ViewVontainer, Zoom, GeoJSON, GeoJSONLayer, Marker, useMapInstance, useMapEvents, useEvents, getCrsRd, etc.
- [arm-cluster](packages/arm-cluster) - exports MarkerClusterGroup (using leaflet.markercluster)
- [arm-nontiled](packages/arm-nontiled) - exports NonTiledLayer
## Usage
- `npm install --save @amsterdam/arm-core`
- `npm install --save @amsterdam/arm-cluster`
- `npm install --save @amsterdam/arm-nontiled`
## NPM
- [@amsterdam/arm-core](https://www.npmjs.com/package/@amsterdam/arm-core)
- [@amsterdam/arm-cluster](https://www.npmjs.com/package/@amsterdam/arm-cluster)
- [@amsterdam/arm-nontiled](https://www.npmjs.com/package/@amsterdam/arm-nontiled)
## Docs
- [Getting Started](https://github.com/Amsterdam/amsterdam-react-maps/tree/master/docs/GETTING_STARTED.md)
- [Contributing](https://github.com/Amsterdam/amsterdam-react-maps/tree/master/docs/CONTRIBUTING.md)
- [Changelog](https://github.com/Amsterdam/amsterdam-react-maps/tree/master/CHANGELOG.md)
- [Maintainers](https://github.com/Amsterdam/amsterdam-react-maps/tree/master/docs/MAINTAINERS.md)
- [Code of Conduct](https://github.com/Amsterdam/amsterdam-react-maps/tree/master/docs/CODE_OF_CONDUCT.md)