A page showing a list of Communities that pops to a map.

On-chain
Lightning
Lightning Contactless

Describing the Payment Type colouring.

Add a single Android icon on the website that pops a modal for GitHub, F-Droid and Play Store.

Perhaps add in some text about why we encourage F-Droid and Google can get in the bin.

• Copy
• Design
• Dev

Copy

Noobs

Simply fill out the form and we will add the location into OpenStreetMaps for you!

Field: Merchant Name
Field: Address
Field: Google Maps URL
Radio: onchain | lightning | ightning contactless/nfc
Field: Notes | Please enter as much detail as possible.

You'll be editing like a Super Shadowy Coder in no time.

Shadowy Super Coders

Once you have an OpenStreetMap account, you can use the OSM iD web app to edit the maps directly on OpenStreetMap.org.

Please use the following guidance when editing locations:

Required tags

currency:XBT=yes - This denotes the Bitcoin currency is generally accepted.

Optional tags

payment:onchain=yes - This denotes that onchain payments are accepted.

payment:lightning=yes - This denotes that Lightning payments are accepted.

payment:lightning_contactless=yes - This denotes that NFC Lightning payments are accepted.

survey:date=yyyy-mm-dd - This helps mappers know how current the data is. You should verify all data if using this.

Legacy tags

payment:bitcoin=yes - This is a very popular legacy tag implying both currency:XBT=yes and payment:onchain=yes.

currency:BTC=yes - This is a less popular tag, although has some use.

We still search for these tags for general display in the apps, but we won't be specific on the payment types supported. You should consider removing them and updating with the current tagging rules.

Points, not Ways

Please tag points not ways. If ways already exist, consider adding a point.

Group the noob form submissions by country or region to make it easier for shadowy supertaggers to find the submissions they are interested in.

The Discord #location-submission channel is getting messy AF.

The Noob Form on the website should create a new issue in the btcmap-data repo with a location-sumbission tag. Perhaps even giving the submitter the issue ID so they don't hound me via twitter DMs!.

The Discord bot should announce when an issue is opened and closed.

I'd be open to nuking the channel as it makes my head hurt and using the data table back end to create the backlog issues, recognising there will be a handful of dupes.

Issues also help those not on Discord to engage with the project and allow me to share web links when seeking help.

When I explore Warsaw via btcmap.org I do see lot of places... but these are almost exclusively ATMs or exchanges.

It would be really useful to filter out locations by their coarse category, such as Shops, Food (cafe/restarant/fast_food/etc).

https://coinmap.org/view/ has done something like that.

Question is how coarse/detailed should categories be. Maybe https://www.openstreetbrowser.org/ categories could be used?

For example, show everything by default. I you want, you can select only "Leisure, Sport and Shopping" group, or if you want only places to eat, select "Gastronomy" subgroup. I doubt there's need to go into more detail, i.e. restaurant/cafe/fast_food/etc.

We should be able to setup communities in the /community space.

This would show a page with node information for that area (bounded rectangle for now) with an embedded map from the API for that area.

API would focus on geographical area e.g. /area/london. Communities focussing on the local vibe, e.g. /community/london-bitcoin-space.

/community/london-bitcoin-space page should embed a map and only load locations from the attached /area/london endpoint.

Could include social info for that community and eventually meet-up info at OSM locations we know.

MVP required.

To enable an embedded map to only show 'merchants accepting bitcoin lightning contactless payments'.

i.e. payment:lightning_contactless=yes

Points, Lines and Area.

Update Embedding Guidance when known to prevent cross-site geolocation errors.

For donation CTAs.

This enables people to pick the location of the place, greatly reducing the effort for taggers.

Is your feature request related to a problem? Please describe.
I Suggest add captcha or something proving humanity to prevent spam entries on
https://btcmap.org/add-location

Also Text input for address should have a note something on the line of (locations require a physical address OSM doesnt do service areas. If you are a service industry and do not provide client walk-in make note of it in the description.)

Without any specific payment tags (i.e. just currency:XBT=yes or payment:bitcoin=yes) we should show all three icons (bitcoin/on-chain, lightning and contactless bars) greyed out.

We colour them when we have a specific payment:blah=yes tag and we strike them out if we see a 'payment:blah=no' tag.

@dadofsambonzuki : This should feed the Noob bot.

Commented by @dadofsambonzuki :
We can go further with the Add 2 Home Screen (A2HS) features.

https://github.com/mdn/pwa-examples

Add a "show on map" button for each shadowy supertagger, to see where they are most active.

Add ESLint and Typescript to improve code quality and maintainability, and automate running them on staged files prior to commits using lint-staged and husky (husky added in #31).

Will be adding the following packages:

• https://github.com/eslint/eslint
• https://github.com/okonet/lint-staged
• https://github.com/sveltejs/eslint-plugin-svelte3
• https://github.com/typescript-eslint/typescript-eslint

Using this guide.

I am available to work on this if we'd like to add.

Reduce the point clustering to make it easier to have an overview of the exact locations of merchants.

• Updated icons for payment types
• NFC should be Lightning Contactless
• 'Shadowy supertagger' left aligned
• Twitter handle to be split in Merchant handle and Submitter handle
• 'Help Us Improve' centrally aligned or switched to the 'Support Us' page if ready.

We should add something at the bottom of the page showing us as Silver Sponsors and linking to their sponsors page.

For different merchant types, we could just choose maybe the 5-10 most popular ones to start?

While there is button that generates sharable link to the Bitcoin-accepting location you clicked on, there's no way to send link to the arbitrary position and zoom level.

For example, OSM official map addes #map=12/52.2399/21.0361 on every move of the view: https://www.openstreetmap.org/#map=12/52.2399/21.0361 )

Tighten language:

Easily find places to spend sats anywhere on the planet.

You can pan around the world for eternity!

Only one 'world' is populated with pins.

Can we limit the panning to one Earth?

Communities to be shown on main map, perhaps as a layer that can be toggled.

Pin should be at the centre of the community.

I don't think we should show the bounds of the community on the main map.

**

Description:**

This is a small bug. At least at the first load zoom level for the map, the kilometre text is cut off ever so slightly.

To Reproduce:

1. Go to 'btcmap.org/map'
2. See error in bottom left corner on desktop.

Screenshots

Desktop (please complete the following information):

Smartphone (please complete the following information):

Bring icons inline with map pop-up payment types.

Screenshot_20221002-070113~2.png

It's not necessary to login into OSM page and jump right into editing if you just want to see all the mapping details (OSM tags, history, etc).

Having "Details" (or similar) link inside location popup referring to https://www.openstreetmap.org/node/10106876793 instead of https://www.openstreetmap.org/login?referer=%2Fedit%3Fnode%3D10106876793 would help.

To be:

We use OpenStreetMap to properly tag places where you can spend Bitcoin and we display that data in our beautiful apps.

Our apps and the underlying data are free and open source.

Tag it and they will come.

The OSM edit link in the edit icon on the location bubble are not connected to the correct OSM node IDs.

iFrame needs to be able to centre on a a co-ordinate set at a specified zoom level as local meet-ups will want to display for their area only.

Currently, locations can be added without any sort of verification process and data may be outdated/irrelevant (see @nerd2ninja and @majormajor posts here. We could implement a Stacker News style tipping system where users can tip posts that are accurate, or pay to "downvote" posts that are inaccurate, providing some sort of validity score. This would not only help incentivize posting, but would help provide trust and give users easy recourse when they encounter inaccuracies. We could implement this via WebLN, and users could interact with the site via WebLN client such as Alby.

Further discussion would be needed to spec out the exact design. Happy to tackle implementation if we decide to implement!

Allow users to enter raw coordinates on the noob form.

The marker should show the location on the map once both fields have been filled.

Perhaps under a 'Do you already have a crappy Google Map?' section.

Check out OpenLayers and Leaflet.