OpenLayers3 VS Openstreetmap

You probably know this, but in Google Maps at least, you can use browser zoom (ctrl/cmd +/-) to change the size of labels without zooming into the actual map.

------

Speaking of maps, I got to work a fun zoom project a few years ago: https://map.fieldmuseum.org/

We used https://openlayers.org/ and thought long and hard about how to best handle zooming and variable levels of information density & visual hierarchy. If you zoom all the way out, we just highlight where the building is relative to the surroundings. As you start to zoom in, we start to highlight major exhibitions and entrances. Then as you zoom in more, we start showing recommended paths, smaller exhibitions, etc. The label sizes try to scale up and down at each level, smoothly, in order to balance readability and density.

Eventually you can reach the max zoom level and the labels will just grow bigger and bigger, but the SVGs dynamically shrink so they remain pictograms and not just contextless-lines.

Then if you keep going, you eventually find microscopic easter eggs :)

The code is pretty jank (and abandoned), but it's FOSS vanilla JS/HTML/CSS, and the only dependency is on OpenLayers: https://github.com/arcataroger/openlayers_indoor_map

In order to display the GeoJSON features on a map, we will use OpenLayers, which is a very powerful open-source mapping library that is also very simple to use.

OpenLayers is available via the ol npm package, offering developers a powerful toolkit for creating sophisticated maps. Here is a JavaScript implementation that utilizes OpenLayers to showcase a map:

Official Website: https://openlayers.org/

For web maps I'd strongly recommend using OpenLayers. While it's less convenient to get started with compared to the alternatives it's also much more feature-complete and you'll likely hit a ceiling in terms of functionality much later than you would with the others.

Contributing is simple:

1. When you see a trail or any other feature that doesn't appear on the map, take a picture.

2. When you get home, visit https://www.openstreetmap.org and start drawing.

The website has satellite images overlayed wirh map data, so it's easy to see what you are doing.

You can look at your pictures to remind yourself of what was missing.

If you have recorded your ride,you can also upload your GPX trace to OpenStreetMap to make it easier to trace features that don't show up clearly on satellite images.

What impressed me was that it looks like openstreetmap shows the bridge as down already.

https://www.openstreetmap.org/#map=16/39.2144/-76.5279

Through the Fast Forward program, we give free services and support to open source projects and the nonprofits that support them. We support many of the world’s top programming languages (like Python, Rust, Ruby, and the wonderful Scratch), foundational technologies (cURL, the Linux kernel, Kubernetes, OpenStreetMap), and projects that make the internet better and more fun for everyone (Inkscape, Mastodon, Electronic Frontier Foundation, Terms of Service; Didn’t Read).

Way overdue. OpenStreetMap's website at openstreetmap.org is its calling card, and for the past few years the default style shown (called Carto) has all but stagnated in development. Accepted features like highway=busway (introduced three years ago) are not rendered there because the maintainers can no longer be bothered, or dislike the tag personally despite broad community backing.

What worries me for this new effort is that Paul Norman is one of the two remaining Carto sometimes-active maintainers who refuse to merge contributed PRs or even provide alternative minimal support for features like highway=busway, leading to awkward gaps on the baseline map shown on openstreetmap.org.

I would love to be surprised in a positive way about this new effort, but I'm not holding my hopes up. Thankfully OpenStreetMap can be thoroughly useful in apps like OsmAnd and OrganicMaps, and the tile-based Tracestrack Topo layer on openstreetmap.org is getting quite decent:

https://www.openstreetmap.org/#layers=P

https://www.hotosm.org/tools-and-data runs software that's used for example after an earthquake. The tasking manager specifically is a reactjs app plus postgresql with plenty of open issues. HOTOSM has full-time staff, I'm not sure if the developers are full-time, but it's more organized than a volunteer project.

https://github.com/openstreetmap/openstreetmap-website/ is Ruby on Rails (easy installable with a docker setup). The maintainers have trouble even reviewing incoming PRs so an experienced person who can triage, test, review is currently needed.

If you're in the US then https://en.wikipedia.org/wiki/Code_for_America might be worth having a look at.

https://summerofcode.withgoogle.com/ will soon annouce vetted organizations who do open source. (last year https://summerofcode.withgoogle.com/programs/2023/organizati...). Project are paid, the process is long though, all summer. https://developers.google.com/open-source/gsoc/timeline

> 9450 S. W. Barns Rd

Portlandians: Are Barns Rd and Barnes Rd the same thing? Looks like a nice spot if so: https://www.openstreetmap.org/#map=18/45.50901/-122.77468

That building is now a SFX agency: https://hellohinge.com/ (No relation to the dating app)

Also curious if the TEKsystems employment agency next door took its name from Tektronix.

Yes, https://www.openstreetmap.org has quite inconsistent detail as it relies on people mapping stuff.

And help is welcome, anyone can join and help with mapping!

It's shown on OpenStreetMap, but not as a street: https://www.openstreetmap.org/#map=16/51.3682/1.0330