This year, OpenStreetMap US stepped forward to become a steward of Field Papers for the community going forward. The transition makes sense; not only is the tool used extensively by the mapping community globally and in the US, it is also used a great deal by educators through OpenStreetMap US’s TeachOSM program and other education initiatives
While it will now be under the umbrella of OpenStreetMap US, Field Papers will be maintained as a global tool available for mappers around the world. In the next year, OpenStreetMap US will be working to develop a plan for maintenance and development that pulls in the knowledge and skills of the volunteer community, as well as expanding the financial resources available to the project.
Bunting Labs’ new API to download OSM data is looking good. I’m not an OSM power user and every time I try to use Overpass to download some data from OpenStreetMap, I’d struggle for an hour and then download one of Geofabrik’s Shapefiles instead. Overpass is extremely powerful, but its syntax is just as hard to understand—which is ok; powerful software is always complex.
The new API is less powerful but more approachable for occasional users like me. It abstracts away much of OSMs complexity, providing a simpler syntax for accessing data via HTTP requests, and it returns neat GeoJSON data.
So far, Placemark, a bootstrapped one-person project, was only available for paying customers. Now Tom released a free tier, Placemark Play, which provides the same user interface and similar features as the paid tier. The main difference to the paid tier is that Placemark won’t save your data; once your browser session ends, your data is gone.
Without data storage, Placemark Play can be compared to Geojson.io, which handles data persistence similarly, although Geojson.io offers to restore data from the last session. Placemark, however, provides a slicker user interface and more advanced geometry operations (buffers, simplification, convex hulls), imports and exports from and to various geospatial data formats, and design and export map styles for MapboxGL and Leaflet.
Placemark Play is a great option for quick data visualisation and advanced editing, when you need a little more capabilities than Geojson.io.
Rebecca Bellan and Ingrid Lunden, reporting for TechCrunch:
Last month, when transportation startup Via raised $110 million at a $3.5 billion valuation, CEO Daniel Ramot said it planned to make acquisitions to grow its transportation technology stack. Now, a piece of that strategy is falling into place: today the company is announcing its acquisition of Citymapper, the London startup that produces a popular urban mapping app.
I always loved Citymapper. When it came out, it offered a better experience for public-transport routing than Google Maps. I remember moving to London, and Citymapper was a lifesaver; I could not imagine how anyone would navigate the city without it.
But then, I never understood how they were making money—if any. Citymapper offers memberships, which enable additional routing modes, but I don’t think bus-only routing convinces many people to pay for the service. They also sold public-transport passes in London at discounted rates and, more recently, the app’s free tier contained ads. This acquisition is about talent and technology rather than removing a competitor from the field.
AWS is extending Amazon Location Service, their range of geospatial products, with “Open Data Maps”. It offers four base maps developers can use as background maps in their applications: A light and dark standard map, plus a light and dark monochrome design as a background for data visualisations. The maps were designed by Stamen and are mainly based on OpenStreetMap data via Daylight.
Open Data Maps will be a serious option for organisations with high usage, which serve more than 200,000 tiles each month. The pricing for map tiles is quite competitive and lower than that of similar products from Mapbox or MapTiler.
After OSMCha, OpenStreetMap US now also supports MapRoulette as a Charter Project.
MapRoulette is a vital tool within the broader OpenStreetMap ecosystem, guiding mappers to areas needing contributions.
MapRoulette serves the mapping community as a user-friendly tool for systematic improvement of completeness, quality and accuracy of map data. Mappers from over 70 countries review more than 40,000 tasks a month. More than 330,000 changesets in 2022 alone can be directly attributed to MapRoulette.
With Charter Projects, OpenStreetMap US aims to ensure long-term stewardship of critical open-source tools for OpenStreetMap. It provides projects with a home and the ability to raise funds for further development.
OGC Web Map Service (WMS) layers (Yes, they still exist),
A terrain extension allows developers to render 2D data on a 3D surface, and
Collision filters, hiding overlapping features and resulting in cleaner visualisation of dense data.
Deck.gl doesn’t get much recognition, but it looks like a serious web-mapping toolkit.
The market for open-source web-map libraries is getting crowded again. Some classic libraries are still around: OpenLayers, Leaflet, and MapboxGL (technically not open-source). With MapLibre, Gleo, and Deck.gl, some promising new implementations are on the rise. Technology-wise, map front-ends have stalled in the last couple of years. I hope this newfound competition results in advancements in the field.
Mapstack, launched this week, aims to become a central catalogue for open data, a place where you discover and access datasets to fulfil your geo-data needs:
mapstack will do for open map data what GitHub did for open source, by bringing all of the world’s open maps together in one place and making them easy to discover, easy to access and easy to use.
Most of Mapstack’s functionality is currently centred around creating datasets and providing appropriate descriptions for the data. Setting up a new map involves several steps, including creating a new workspace or team, adding members, and providing a description.
Then you proceed to create the actual dataset. Upload your data, currently limited to GeoJSON and files smaller than 50MB. Then select the fields to keep and provide human-readable names. A downside is that you can’t skip this step. You have to go through each chosen field and individually confirm the label. To finalise, provide more information about the nature of the data, its geographic area, and the feature type, which creates an editable name for your new dataset.
That’s a lot of steps before you can view your dataset for the first time. Much of the information can be done after the project is set up. With the goal of discoverability in mind, however, and considering how badly many datasets are missing meta-data, you could say it’s smart design to force users to provide context.
Once the map is created, the features are limited: You can browse the data, view the attribute of features, and apply filters. There’s an attribute table, which is only available for filtered results, but not for the unfiltered data. Mapstack focuses on hosting data and making the data discoverable rather than on interacting, editing or visualising data.
As such, Mapstack is not a competitor of Felt or Placemark, two products released last year that aim to modernise how we do GIS on the Web. Mapstack complements both, and GIS tooling in general, by providing the data for the tools.
Will it take off? I’m not sure. The marketing copy draws comparisons to GitHub, but there are differences. GitHub became successful because it built on a protocol that developers already used and provided a product for collaboration around the protocol. GitHub added value to the developer’s daily work, so a lot of code ended up on the platform.
Mapstack doesn’t tie in with existing tools. Currently, there is no tooling to create or manage data, collaborate or visualise the data. It’s a place where the result of data processing might be hosted. Open data providers have invested in the infrastructure to host data—it’ll be hard to convince them to migrate to Mapstack instead.