jimmyrocks
Joined 14 years ago
Joined 14 years ago
Really great idea to compress the spatial data into Paths.
I would suggest using Natural Earth data instead of OSM so you could drop the ODbL license.
It’d also be really cool if you included the tool that converts the spatial data into Paths.
I maintain a heavily used map of the US, and I found that storing data/serving in vector format seems to be the most efficient (on AWS s3 / DO spaces), and converting to raster in the browser or with a service call / lambda really opens the doors to a lot more use cases. I suspect parent can talk more about this than I can.
We are building the next generation of web map authoring tools using Angular, TypeScript, JavaScript, Python, PostgreSQL/PostGIS, CARTO and Mapbox, and other open source tools.
Frontend Developer: https://chp.tbe.taleo.net/chp02/ats/careers/requisition.jsp?...
There are established ways to combat this (peer review, data stewards, reputation scoring) and even OSM has a checkbox for further validation.
OSM will never fit every use case, but it's good to understand where it falls short and can improve.
I have given a few talks about using OSM data in the US government and it comes down to authoritative data sources and validation. It's a great starting point, but there needs to be another layer (or two) of validation before it can be used at the enterprise level. The National Map Corps has some good examples of how this can be implemented with data stewardship.
I am also working on a few projects to take public domain data and put it into OSM. While it's useful and mostly open, it's definitely less open than the original data sources. Another issues is that as soon as someone edits the imported data, it will become less authoritative as well.
They also have been a big part of supporting the GeoNYC group and helping to organize the OpenStreetMap US conferences.
Thanks for all the maps and data Mapzen!