Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(map): initialising map #3938

Merged
merged 12 commits into from
Feb 9, 2024
Merged

feat(map): initialising map #3938

merged 12 commits into from
Feb 9, 2024

Conversation

siddhart1o1
Copy link
Member

No description provided.

.github/labeler.yml Outdated Show resolved Hide resolved
@siddhart1o1 siddhart1o1 changed the title feat(blink-map): initialising blink map feat(map): initialising map Feb 4, 2024
@siddhart1o1 siddhart1o1 added map and removed consent labels Feb 4, 2024
@siddhart1o1 siddhart1o1 force-pushed the feat--initialising--blink-map branch from dc38a16 to 5a99f27 Compare February 7, 2024 09:25
apps/map/codegen.yml Outdated Show resolved Hide resolved
zoomControl: true,
maxZoom: 38,
minZoom: 3,
styles: [...theme, ...unwantedMarkers],
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what does unwantedMarkets means? why is it useful?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove unnecessary noise/markers from maps. Otherwise, there is too much information on the map.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But where do those markers come from?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assuming it comes from Google maps api, it seems Google maps charge for every single piece of information requested. So if we have to turn all that off, I would think there might be a way to not ask those informations in the first place, which would limit our billing

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assuming it comes from Google maps api, it seems Google maps charge for every single piece of information requested. So if we have to turn all that off, I would think there might be a way to not ask those informations in the first place, which would limit our billing

Map charges are based on the number of loads; hiding or displaying marker information does not affect it.
https://mapsplatform.google.com/pricing/

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok I don't really understand the detail but I think that is fine. We should ensure that the API key we created is protected by a browser referrer or something like that to ensure it's not used abusely; this is how we could ends up with a large bill, probably like the experience Lee had.

@nicolasburtey
Copy link
Member

the "center me" appears to be totally off on my computer (I didn't approve the request when asked to see how that would react... so I would assume it should be a no-op in that case, but it still zoom in in a "random" point in the middle of El Salvador)

@siddhart1o1 siddhart1o1 marked this pull request as draft February 7, 2024 21:31
@siddhart1o1
Copy link
Member Author

the "center me" appears to be totally off on my computer (I didn't approve the request when asked to see how that would react... so I would assume it should be a no-op in that case, but it still zoom in in a "random" point in the middle of El Salvador)

Yes, I know. I was working on it; it's fixed now. Now, the pointer will only be shown if the user allows their location.

@siddhart1o1 siddhart1o1 force-pushed the feat--initialising--blink-map branch from e0a6a40 to efef738 Compare February 7, 2024 21:50
@siddhart1o1 siddhart1o1 marked this pull request as ready for review February 7, 2024 22:32
@siddhart1o1 siddhart1o1 force-pushed the feat--initialising--blink-map branch from ab67f41 to cfff024 Compare February 8, 2024 11:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants