Error with TileMill and OpenStreetMap Carto project

I have been trying to load the OpenStreetMap carto project in order to export tiles for use on our in house GIS Server. I have followed all the instructions up to loading the osm xml into postGIS and postgresql. I have viewed the data in QGIS and it is working. I downloaded the open-street-map-carto project from github and changed all the configuration files to point to our server. I am at a point where I am unable to view anything in TileMill and I am receiving this error "water-features.mss:159:8 Property text-name required for defining text styles." I am not sure what the issue is and how to fix it.

Here is the code for water-features.mss

@breakwater-color: #aaa; /* Also for groyne */ @dam: #adadad; @dam-line: #444444; @weir-line: #aaa; @lock-gate: #aaa; @lock-gate-line: #aaa; #water-barriers-point, #water-barriers-line, #water-barriers-poly { [waterway = 'dam'] { #water-barriers-poly[zoom >= 13] { line-width: 2; line-color: @dam-line; line-join: round; line-cap: round; polygon-fill: @dam; } #water-barriers-line[zoom >= 13] { line-width: 2; line-color: @dam-line; line-join: round; line-cap: round; } #water-barriers-point[zoom >= 17] { marker-fill: @dam; marker-line-color: @dam-line; marker-line-width: 1; marker-width: 8; marker-height: 8; marker-allow-overlap: true; marker-ignore-placement: true; } } [waterway = 'weir'] { #water-barriers-line[zoom >= 13] { line-color: @weir-line; line-width: 2; line-dasharray: 2,2; } #water-barriers-point[zoom >= 17] { marker-fill: @water-color; marker-line-color: @weir-line; marker-line-width: 1; marker-width: 8; marker-height: 8; marker-allow-overlap: true; marker-ignore-placement: true; } } [waterway = 'lock_gate'] { #water-barriers-line[zoom >= 13] { line-color: @lock-gate-line; line-width: 2; } #water-barriers-point[zoom >= 17] { marker-fill: @lock-gate; marker-line-width: 0; marker-width: 8; marker-height: 8; marker-allow-overlap: true; marker-ignore-placement: true; } } } #piers-poly, #piers-line { [man_made = 'pier'][zoom >= 12] { #piers-poly { polygon-fill: @land-color; } #piers-line { line-width: 1.5; line-color: @land-color; [zoom >= 13] { line-width: 3; } [zoom >= 16] { line-width: 7; } } } [man_made = 'breakwater'][zoom >= 12], [man_made = 'groyne'][zoom >= 12] { #piers-poly { polygon-fill: @breakwater-color; } #piers-line { line-width: 1; line-color: @breakwater-color; [zoom >= 13] { line-width: 2; } [zoom >= 16] { line-width: 4; } } } } #marinas-area { [zoom >= 14] { a/line-width: 1; a/line-offset: -0.5; a/line-color: blue; a/line-opacity: 0.1; a/line-join: round; a/line-cap: round; b/line-width: 3; b/line-offset: -1.5; b/line-color: blue; b/line-opacity: 0.1; b/line-join: round; b/line-cap: round; [zoom >= 17] { a/line-width: 2; a/line-offset: -1; b/line-width: 6; b/line-offset: -3; } } } .text { [feature = 'waterway_dam'], [feature = 'waterway_weir'] { #text-poly[zoom >= 15], #text-line[zoom >= 15], #text-point[zoom >= 17] { text-name: "[name]"; text-halo-radius: 1; text-halo-fill: rgba(255,255,255,0.6); text-fill: #222; text-size: 10; text-face-name: @book-fonts; #text-poly { text-placement: interior; } #text-line { text-placement: line; text-dy: 8; text-spacing: 400; } #text-point { text-placement: point; text-dy: 8; } } } [feature = 'man_made_breakwater'][zoom >= 15], [feature = 'man_made_groyne'][zoom >= 15], [feature = 'man_made_pier'][zoom >= 15] { #text-poly, #text-line { text-name: "[name]"; text-halo-radius: 1; text-halo-fill: rgba(255,255,255,0.6); text-fill: #222; text-size: 10; text-face-name: @book-fonts; #text-poly { text-placement: interior; } #text-line { text-placement: line; text-spacing: 400; } } } }

I'm the author of this particular code, but I'm not sure what could cause this.

Do you have the latest Tilemill version?

Maybe you could try using an older openstreetmap-carto version, for example 2.28.0:

Also, does duplicating the code, like this, help by any chance?

#text-poly { text-name: "[name]"; text-halo-radius: 1; text-halo-fill: rgba(255,255,255,0.6); text-fill: #222; text-size: 10; text-face-name: @book-fonts; text-placement: interior; } #text-line { text-name: "[name]"; text-halo-radius: 1; text-halo-fill: rgba(255,255,255,0.6); text-fill: #222; text-size: 10; text-face-name: @book-fonts; text-placement: line; text-spacing: 400; }

I can't reproduce this locally, so I'd be happy to know what causes this.

Error with TileMill and OpenStreetMap Carto project - Geographic Information Systems

  • accounting
  • ajax-framework
  • application-framework
  • audio-editor
  • automation
  • big-data
  • blog-engine
  • browser
  • build-tool
  • business-process-management
  • cache
  • charting-library
  • chat-server
  • code-coverage
  • collaboration
  • column-database
  • document-management
  • data-extraction
  • database
  • e-commerce
  • email-client
  • embedded-database
  • enterprise-search
  • erp
  • facebook-alternative
  • faq-system
  • finance
  • forum-software
  • ftp
  • full-text-search
  • game-engine
  • geocoding
  • git
  • graph-database
  • healthcare-information-system
  • helpdesk
  • html-parser
  • html-to-text
  • human-resource-management
  • identity-management
  • image-compression
  • information-retrieval
  • instant-messaging
  • intrusion-detection-system
  • issue-tracking
  • java-framework
  • java-games
  • jquery-plugin
  • json
  • jvm
  • key-management
  • key-value-store
  • language-detection
  • linux-operating-system
  • linux-tools
  • log-analysis
  • mail-client
  • mail-server
  • mailing-list
  • media-player
  • media-server
  • message-queue
  • micro-blogging
  • mobile-framework
  • natural-language-processing
  • network-management
  • networking-library
  • neural-network
  • no-sql
  • nodejs
  • oauth
  • object-database
  • ocr
  • office-suite
  • online-shopping
  • operating-system
  • orm
  • package-manager
  • pdf-library
  • personnel-finance
  • photo-management
  • programming-language
  • proxy-server
  • qa-tools
  • qr-code
  • question
  • records-management
  • relational-database
  • reporting-tool
  • rrdtool
  • school-management
  • screen-capture
  • search-engine
  • server-monitoring
  • shopping-cart
  • skype-alternative
  • sms-library
  • social-networking
  • testing-tool
  • text-extraction
  • text-to-speech
  • ticketing
  • twitter-client
  • ubuntu-fork
  • uml-tool
  • unit-testing
  • url-shortning-service
  • version-control
  • video-cms
  • video-conference
  • video-player
  • virtualization
  • visualization
  • voip-server
  • vpn
  • web-analytics
  • web-application-framework
  • web-browser
  • webcrawler
  • webserver
  • wysiwyg-editor
  • xml-parser
  • xmpp
  • xps-viewer
  • zip
  • zlib

OSM-realtime-update - :clock2: OpenStreetMap Data Extracts - updated on the fly!

A service providing real-time OSM data. The frontend allows manipulating tasks and serves the OSM data produced by the tasks.

Tags openstreetmap pbf mapping nodejs
Implementation Javascript
License MIT
Platform OS-Independent

OsmAnd (OSM Automated Navigation Directions) is a map and navigation application with access to the free, worldwide, and high-quality OpenStreetMap (OSM) data. All map data can be stored on your device's memory card for offline use. Via your device's GPS, OsmAnd offers routing, with optical and voice guidance, for car, bike, and pedestrian. All the main functionalities work both online and offline (no internet needed).

One click download and import of OpenStreetMap and terrain for Blender! Global coverage! Documentation is hosted here.

uMap lets you create maps with OpenStreetMap layers in a minute and embed them in your site. Because we think that the more OSM will be used, the more OSM will be ''cured''. It uses django-leaflet-storage and Leaflet.Storage, built on top of Django and Leaflet. See developer documentation.

OSM Bright is a sensible starting point for quickly making beautiful maps based on an OpenStreetMap database. It is written in the Carto styling language and can be opened as a project in TileMill.The style is still a work in progress and you are encouraged to use the issue tracker to note missing features or problems with the current implementation.

Grid_map - Universal grid map library for mobile robotic mapping

This is a C++ library with ROS interface to manage two-dimensional grid maps with multiple data layers. It is designed for mobile robotic mapping to store data such as elevation, variance, color, friction coefficient, foothold quality, surface normal, traversability etc. It is used in the Robot-Centric Elevation Mapping package designed for rough terrain navigation. The grid map package has been tested with ROS Indigo, Jade (under Ubuntu 14.04) and Kinetic (under Ubuntu 16.04). This is research code, expect that it changes often and any fitness for a particular purpose is disclaimed.

Agrégateur de flux

Good day. Живу я хорошо, у меня почти всё есть. Вот, решил воспользоваться "открытыми уличными картами" для своего самопального проекта.

" User's Diaries": 1111

Оказывается, профиль на форуме теперь привязан к профилю на сайте, причём по нику. Сменил ник и вуаля - на форум под старым ником не зайти. Забавно.

Jochen Topf: Antarctica in OpenStreetMap

OpenStreetMap wants to map the whole world, but there is a whole continent that has been neglected a bit: Antarctica. Of course there isn’t much there besides rocks, ice, and penguins and not too many people live there. But still, it is a huge area and it should appear properly on our maps.

I have looked into the current situation and what could be done and want to write that up here as a first step towards improving the situation.

The Mercator projection generally used in online maps only covers the area between about 85.0511 degrees South and 85.0511 degrees North. While this is not a problem in most cases, it obviously is a problem for Antarctica. JOSM can edit data South of -85.0511 degrees when you change the projection from Mercator to “WGS84 Geographic” (EPSG:4326), but Potlatch can’t. And the usual aerial images aren’t available, because they also use the same Mercator projection.

If the source tags are right, the coastline seems to have been mostly imported from GADM. Apart of the licensing issues, this data seems to be old and not very accurate. The real coastline dips below 85.0511 degrees South in the Ross sea, but in OSM it is cut off there, probably because not many people are actually creating maps not using the Mercator projection. There are newer and better sources for the Antarctica coastline around and it should not be too difficult to throw the current one out and replace it by a better one.

There are huge ocean areas around the land mass of the continent that are covered in ice shelves. They should be tagged and appear on the map because they are large features and they affect the way we perceive Antarctica.

There is no tag for ice shelves yet, there is natural=glacier, but that is not the same. I propose adding a tag natural=ice_shelf for this. There are sources for the borders of the ice-shelf, so it wouldn’t be a big problem to add them.

Bing and Mapbox seem to be using older and not very detailed Landsat images. There are newer Landsat images with better resolution available, see below. Landsat images don’t go below 82.5 degrees South because of the orbit of the Landsat satellites. The images from MapQuest Open are better, they are from Landsat and mostly from NASA’s BlueMarble NG.
Data Sources

If you want to have a look around, maybe try out some of the data yourself, here are some pointers.

I have asked Frederik and he has added Antarctica to the list of OSM extracts that are generated daily and published on It is not much data and you can load all of it into JOSM, though it will be a bit slow then.

The current OSM coastline is available from, it is usually updated daily.

There are several sources of reasonably current data that seem to be quite accurate and detailed.

The Mosaic of Antarctica (MOA) contains good satellite images for Antarctica and, derived from it, shapefiles. You can look at them and download the shape files. It seems that Natural Earth Data derives their Antarctica coastlines from these. The shape files can’t be used directly for import, though, because the vectorization is bad and the data contains lots of ziggzaggy lines.

Another data source could be the Landsat Image Mosaic Of Antarctica (LIMA) and derived data. You can look at the images or the Research Atlas. There are also downloads and WMS available.

(Thanks to Christoph Hormann for these links and insights into the data.)

There are also several more links on the wiki on the Antarctica page. I haven’t looked at all of them yet.

Of course we have to look into the details, but licensing should not be a big issue. Almost all of this data is ultimately derived from NASA satellite images or other satellite data which is in the Public Domain. Either NASA themselves or other US government or research agencies have been processing this data to create the data that is available at the places mentioned above.

I can display all of this data in EPSG:4326 in Quantum GIS (QGIS). The Antarctic Polar Stereographic Projection EPSG:3031 is much better, though. Unfortunately there are some rendering problems with it in QGIS. I haven’t tried Mapnik or other renderers yet. This is something I must explore some more.

There is one other problem with OSM data in Antarctica: Just like the spot in the Atlantic with 0 degrees latitude and 0 degrees longitude, Antarctica seems to attract some bogus data. Most probably from software bugs, but it is also a likely spot to add bogus things for the fun of it without anybody noticing. Last time I looked, I found (and removed), among other strange things, a restaurant, a restroom, and a pub called “Very Cold” somewhere in Antarctica and a parking lot and a tree from failed imports at the South Pole.

I think we can probably just throw away the existing coastline and import the coastline and ice-shelf data from NaturalEarth. We don’t actually need that much detail in Antarctica. If and when we need it we can always add the more detailed data from MOA either in the whole of Antarctica or just in selected areas. This is much less work than cleaning up the better MOA data and making it ready for OSM and we’d still have a large improvement over the current situation. If it turns out that there are areas where the data currently existing in OSM is better than the NaturalEarth data, we should, of course, keep that, or check with the better MOA data.

So far these are just some notes from my research. There is more work to be done. I hope this article will start a discussion. Please tell me if you have any other knowledge, ideas, insights. Before actually doing any kind of import, I will, of course, write up in some more detail what is planned and discuss that according to the Import Guidelines.

Telematics in China (Part 1)

GPS Business News recently met with Ralf Hug, President of The Trajectory Group, a boutique consulting firm specialized in telematics services.

Hug previously worked for Airbiquity, Navigon, Garmin and Mercedes-Benz USA. He has been recently spending a lot of time in China helping clients evaluate th.

" User's Diaries": Треугольник МКАД-Новорязанка-Бетонка-Егорьевка

В сабже нет теперь крупных белых пятен. Обрисовывая бесконечные пустоши, в которые превратились бывшие колхозные поля, много думал. Поле со спутника сразу видно -- на нем слишком правильными рядами что-нибудь да растет. И таких полей в этом треугольнике -- процентов сильно до пяти. Примерно четверть из этих пустошей -- уже под многочисленными КП, СНТ, ИЗ и прочими строениями явно не сельскохозяйственного типа. Интересно, что произойдет лет через 50? Все свободные площади застроят коттеджами, или нынешние коттеджи снесут, а на их месте будут небоскребы и торговые центры?

Nick Whitelegg/Freemap: Contours being regenerated

As you may know I have added a few more counties to Freemap recently, namely Devon, North Yorkshire, Oxfordshire, Buckinghamshire and Shropshire. As a result of this I had to import more OS LandForm PANORAMA contour data to cover some of these areas. However, this has caused some problems.

Seeing as some of the contour data on the boundaries of the new areas was cached (contours are cached by XYZ tile, but are imported by OS grid square) there were some odd artefacts in these boundary areas where an old XYZ tile with formerly partial coverage had been cached resulting in missing contours even with the new contour data.

Therefore, to deal with this – and not wanting to find the “problem” tiles on a case-by-case basis, a tedious task – I am regenerating *all* contour data from scratch. This means that next time you view the map, it might be a few seconds for your area to render, but once this is done, it will be much faster as the data will have been cached.

More generally, I am now caching not only contour data but the actual OSM data itself. This appears to be using less disc space than I anticipated (presumably because many tiles at zoomed-in levels are never looked at) and is therefore more feasible, giving a much faster experience than formerly. It also means that I am able to cover more of the country, so if you have any requests (predominantly rural counties only!) let me know.

Richard Weait: Add a Trail to OpenStreetMap

Let's add a trail to OpenStreetMap.

Multi-use trails add character to a neighbourhood and to a map. Here is a way to add your local trail to OpenStreetMap. This is a suitable first mapping project when you get a GPS receiver, and this is the sort of mapping that you can do with family and friends.

I know from local knowledge that there is a multi-purpose trail in this new neighbourhood. Before our survey, the map does not show the trail.

Grab the GPS and the kids and let's go mapping.

When you get to the trailhead, switch on the GPS and let it acquire a good signal lock. Pop the GPS in your backpack and enjoy a trip around the trail with the family. When done, switch the GPS off. That doesn't seem like such a burden does it? You get a nice outing with the family and you get to do some mapping without them rolling their eyes quite so much.

I believe that this is trail is a loop when complete, I've only surveyed a portion of it so far. That's okay, of course. When contributing data to OpenStreetMap, one may contribute as much or as little as they choose.

Put this trail on the map

When you have some quiet time to edit, get the track file from your GPS receiver and take a look at it with your favourite editor.

Here we see my walk around the trail. I'm a little surprised that the beginning and end of the track file appear to be about 60m apart, when I switched the GPS on and off at approximately the same location. This should serve a a reminder that GPS receivers, and their operators, have limitations. I may have started before the device had a great signal lock, or the reception may have drifted due to satellite movement, local interference or alien attack. Hard to say what the cause is, but I'll have to keep this reception problem in mind as I edit.

Let's get the current OSM data.

I've zoomed out a bit to get some of the surrounding area as well as the extent of my track file. Everything looks about right. Let's start at the beginning and have a look at that surprising separation between the beginning and end of the track file.

My recollection of this trail entry is that it is straight across from Silverthorne Drive. The finishing position is closer to that than the starting position, which suggests that I didn't let the device get a good signal lock, but neither track is right on the nose. I'll go with my memory on this one and put the trail entrance across from the road. I'll connect the trail entrance to the road centerline because the trail does connect to the road. It even has a paved ramp from road level to sidewalk level.

Each of the trail entrances I saw had a small paved section, while the trail itself was gravel. In the screenshot above I have added the paved sections and marked them as

k:highway v:path
k:foot v:yes
k:bicycle v:yes
k:surface v:paved

I'll use this same set of tags for the other trail entrance stubs, so keep the way selected and press [ctrl]-c for copy, as I draw in each stub I can use [ctrl]-[shift]-v paste tags to add those same tags to the currently selected way, rather than retyping them.

I'll add the other entrances now. I have emphasized them in this image for clarity.

Now I'll add an unpaved portion of the trail.

When adding to an existing way, JOSM helpfully continues that way with the same tags. This is mostly-good, but we'll make a small change after adding this section to correct the surface value. After adding the trail, I returned to the entrance stub, and selected the node where the pavement ends. Press p to split the way at that node.

The image above shows that way with the unpaved section selected after splitting. Now correct the surface value for the unpaved portion of the trail. Select the surface value from the properties list, press the edit button, then change the value from paved to gravel and press the save button to close the edit properties dialogue box.

and use [ctrl]-c to save this set of tags for the remaining trail sections. Now I'll add the remaining unpaved portions of the trail.

You'll notice that I don't exactly follow every twist and turn of the track file when I add the highway=path.

Notice the upper right corner of the image above. The track file suggests that I doubled back quickly then continued clockwise along the trail. That isn't what happened. The track file is showing a symptom of a reception problem of some sort. All GPS track files from consumer grade GPS receivers show these types of flaws. So don't be too concerned about them. Also don't try to follow every twist and turn suggested by your track files. Use your notes and observations as well as the track file as a reference.

A few extras for trail mappers

We've added the trail and this survey could be considered complete. I'll add just a few extra items to make things easier for future mappers who may want to improve this area. That future mapper might even be me, so I like to treat future mappers nicely.

Each trail entrance has a gate to prevent unauthorized motor vehicle access. The gates I saw were similar to this one photographed by Bob McMullen, which allows foot and bicycle traffic to pass without opening the gate.

I did not mark the exact location of the gates during my survey but they are each close to the road. I'll estimate their locations. From my imperfect memory, I'll guess that the gate was three metres from the road.

Our map shows the road centerline, so I'll add another three metres and place a gate approximately six metres from the road way as shown above. Then add the appropriate access tags for the gate.

Since this is imperfect and guestimated, I'll also add a note tag for future mappers,

k:foot v:yes
k:bicycle v:yes
k:barrier v:gate
k:note v:gate position estimated

And lastly, I did not survey the complete trail.

There is more trail to walk at each end, so I'll mark them as fixme so interested mappers can find them, survey more of the trail and improve the map even more.

And the final steps are to upload the edits to the OpenStreetMap server using either the upload button on the menu bar, or by pressing [ctrl]-[shift]-u, and adding an informative changeset comment.

k:comment v:Cambridge Ontario, Mill Run Trail, foot survey and "add a trail" tutorial

Gate photo © Bob McMullen is used by permission of the photographer. Thank you Bob!

OSMer, Ed Loach suggested adding the tag k:limbo_dancer v:right for the gate which gave me a nice laugh. Thank you Ed.

Map images and data © 2010 CCBYSA OpenStreetMap and contributors.

This article was originally published on Fri, 08/20/2010 - 01:30.

MapBox blog: Opening Space in San Francisco at Code for America

Starting today MapBox has a new awesome space at Code for America in San Francisco (155 9th Street). We’re increasingly working in the Bay Area and with our team growing rapidly this new space establishes an important permanent presence for us. To start you will find John who is based in San Francisco and myself working from this space. I will be traveling out to San Francisco at least once a month.

Party downstairs, work upstairs at the @codeforamerica offices.

This is not just any office space for us. Code for America does amazing work and the program attracts driven and talented people who want to change the world. Co-working at Code For America lets us not only be around the current fellows but also hang out with our alumni friends using the space as a startup incubator. This is exactly the kind of environment we want to be in.

Join us for drinks tonight at 5pm to celebrate our new space in San Francisco at Bloodhound (Folsom between 8th+7th).

MapBox blog: Mapping the Lights of the Night

The Suomi National Polar-Orbiting Partnership (NPP) is one the newest U.S. Government satellites orbiting the earth, providing beautiful, open public domain imagery, thanks to U.S. taxpayers, and the U.S. Government’s commitment to open data and remote sensing research. Today, I used the VIIRS Nighttime Lights-2012 dataset, maintained by the Earth Observation Group, NOAA National Geophysical Data Center, to create a beautiful webmap showing lights visible at night from space.

Suomi National Polar-orbiting Partnership (NPP)

A Delta II rocket launch with the NPP spacecraft payload, October 28, 2012 at Vandenberg Air Force Base, California (NASA/Bill Ingalls)

The Suomi NPP mission has several science objectives:

  • Monitor and record climate change and natural disasters, including wildfires, volcanic eruptions, droughts, and floods
  • Enhance weather prediction capabilities by collecting information about cloud cover, atmospheric temperatures, and humidity
  • Observe changes in agricultural processes and vegetation patterns, as well as land and ocean ice
  • Record atmospheric, land and sea surface temperatures
  • Monitor the amount of energy entering and exiting our planet’s atmosphere

For an in-depth description of the NPP spacecraft instrument, head over to NASA’s NPP instrument description.

There are five instruments on the Suomi NPP satellite.

  1. The Advanced Technology Microwave Sounder (ATMS), a microwave radiometer, which models temperature and moisture for weather forecasting models
  2. The Cross-track Infrared Sounder (CrIS), an interferometer, which measures atmospheric moisture and pressure for weather forecasting
  3. The Ozone Mapping and Profiler Suite (OMPS) measures the ozone layer
  4. The Visible Infrared Imaging Radiometer Suite (VIIRS) captures visible and infrared imagery to monitor and measure processes including wildfires, land changes, cloud cover, and sea surface temperature
  5. The Clouds and the Earth’s Radiant Energy System (CERES) monitors the amount of energy entering and exiting the atmosphere

The VIIRS Instrument collects visible and infrared imagery, across 22 different channels along the electromagnetic spectrum. There are many potential use cases for VIIRS imagery, including ocean, land, and atmospheric monitoring.

I’m going to go through how you can use VIIRS imagery with the open source geospatial library GDAL and TileMill to visualize nighttime lights visible from space.

VIIRS Nighttime Lights 2012 is a VIIRS derivative product created by compositing day/night bands from images captured between April 18-26, 2012, and October 11-23, 2012, on nights without moonlight. The dataset description goes into more detail about the level of processing, but a few important things to note are that the dataset has not had the background noise subtracted. The VIIRS day-night band detects lights, gas flares, auroras, and wildfires. It also detects reflected moonlight on some extremely bright surfaces, like snow-covered mountains.

  1. Download GeoTIFFs from NOAA, which you can access via ftp at
  2. Once you have the files downloaded, you’ll want to scale the downloaded GeoTiff, which comes with 32bit floating point values ranging from -1 to 50,000, to produce an 8 bit output GeoTiff. Because I was only interested in the areas in which the VIIRS sensor detected light, I used gdal_translate -scale 0 50 -ot Byte to take only those values falling between 1-50, and scaling them to 1 to 255 in the output raster.
  3. Reproject to Google Mercator using gdalwarp
  4. Add overviews to the reprojected GeoTIFF using gdaladdo
  5. Next use gdalbuildvrt to generate three virtual rasters – one for each band of an RGB image. Since the Nighttime Lights dataset comes as a single-band grayscale GeoTIFF, I use virtual rasters to simulate the bands of a natural color RGB image.
  6. Create a fourth virtual raster with the red, green, and blue VRTs generated in step 5
  7. Modify the colors of each band, setting the <ColorInterp> tag, and adding look up tables using the <LUT> tag to the VRT XML
  8. To optimize performance, generate a new GeoTIFF from the RGB-simulated VRT, and add overviews
  9. Open in TileMill, style, and render
  10. Upload to MapBox Hosting, and create a custom high-contrast MapBox Satellite layer base map.

" User's Diaries": Animating GPX files (rendering animations)

I like very much the *.GIF animations that are created from the GPX files and showcased in the OS website. I wonder if somebody knows how can I create those kind of animations? Is there a script or a software I can use to make them my self? I am specially interested in rendering this kind of animations in a bigger format and as well provide a more paced timing ton the animation. Thanks!

Richard Weait: Take a Drive

I like the cartography on . The style differs from our mapnik and osmarender styles by rendering fewer types of objects and by using subtler colors. It's different. Their selectable thematic layers are great and let you add objects to the map that interest you at the moment. That's all pretty cool and that's not what I started this article to talk about.

I want to talk about golf.

I noticed the new, new to me at least, golf course rendering at the other day. They've added a little golf flag to rendered golf course areas. Very nice! They also provide their mapnik style for your enjoyment under the MIT license. Awesome.

Perhaps it's the snow. I'm thinking about golf again and I was working on my swing the other day. That, and Gregory's tweet the other day, got me thinking about doing more with the golf style I started a while back.

Note to self: Would be fun to map & render some golf courses. Using Bing & @rweait 's style.
-- Gregory Marler on twitter

So Gregory is right. It would be fun to do some golf course mapping. I did a little mapping and I did a little cartography. So far this style supports the following tags.

k:golf v:tee
k:golf v:fairway
k:golf v:green
k:golf v:bunker

I've added the stripe effect left by lawn mowers to the fairway and cross-hatching to the greens and tee boxes. Still a lot more to do and I'm having a lot of fun with it.

So far this style is rendered as a simple overlay and I switch backgrounds between MapQuest, mapnik and the simple style from the RTC OpenStreetMap book.

Here's a little look at it. This shows your approach shot on a saucy little par five, number two hole at Savannah Golf Links in Cambridge Ontario. Keep straight and conservative on the fairway for your first two shots and you'll take the marsh on the left out of play. A nice, short iron to the kidney-shaped green should be played to one side or the other to avoid the guardian bunkers.

I hope that you'll enjoy mapping your favorite golf courses. This golf layer will update from the OpenStreetMap so you'll be able to see your mapping rendered. [Note: the golf overlay rendering server is currently off-line]

If you start mapping a golf course, send us a link in the comments below!

Map images and data © 2011 CCBYSA OpenStreetMap and contributors.

This article was origianlly published on Wed, 01/12/2011 - 17:13.

Shaun McDonald: Videos of the talks at Rome 2013

In January I was at the in Rome, and recorded most of the talks that happened. I have now uploaded those talks to YouTube for the wider community to be able to watch. Here’s the videos in the order they were recorded:

ШТОСМ: Открыли MapZen

Chris Hill: A Park, Hawthorn and Rugby

I've been trying to fill the gaps in land use in Hull. I think that, generally, everywhere in a city can and should have a landuse tag and that land use areas probably should join at their edges. I have been joining, say, a residential land use to a commercial land use, sharing the nodes, so there is no gap between them. I have not been joining land use areas to roads. That is just wrong. A few land use areas stop at a boundary with a fence or a hedge, so I sometimes reuse the land use nodes to add a barrier tag, but never a road. Roads are, I think, too complex to be shared with a land use edge. Roads do fall into the land use. I residential road is part of the residential area along with the houses and occasional shop and pub too. Parks, schools, recreation grounds, cemeteries and other large areas I've generally left out of other land use - layering land use on top of, but another land use seems wrong to me. I have tried not use too many multipolygons with land use, so a pond in a park will not be a hole in a multipolygon, though it would work well if it was.

This had involved a lot of staring at aerial imagery followed by surveys to try to determine where one land use type gives way to another. There have also been a lot of areas that seem to have no land use. I have resorted to landuse=grass for space between a river bank and, say, an industrial area nearby. I'm not happy that 'grass' is a land use, but then many OSM tags have grown to be useful without their actual keys or values being completely logical. OSM is about a map database not some kind of taxonomy after all. I have also used natural=scrub in some places too. Again not sure but I think it is better than nothing. It is really urban waste ground, but that doesn't seem to be in the wiki. I have used landuse=railway for the inaccessible land fenced off beside railways which seems right to me. I think there should be a landuse=highway tag for major roads and motorways too. They often have an area of inaccessible land reserved beside them, sometimes beyond the verge perhaps up an embankment. In Britain this is usually grassed sometimes with bushes or small trees on to too. They have become useful wildlife havens.

I noticed on the aerial images a largish piece of grass on the outskirts of the city that I didn't recognise. When we went to look we found a large grassy park so I added that. It was very, very wet - flooded in parts, so I didn't venture onto it, though I will later in the year just for a look around at what lies beyond some trees and bushes and whether they too are part of the park or not.

Part of my work has been focussed on areas of Hull that are being redeveloped - and I haven't completed them yet. Hawthorn Avenue had a lot of terraced streets of it on both sides. Some had fallen into disrepair and even dereliction and the council declared the will to redevelop some of the area. I don't want to give the impression that it was or is a slum. Just some areas where becoming a mess and the houses were getting harder to maintain and costing more to heat, for example. Yesterday we took a look at the work that is progressing. Areas of Woodcock street have been transformed, with a mixture of size and styles of houses, a small park, sensible car parking, cycle ways and foot ways and the whole area looks impressive. I don't know anyone who lives there to see if there is a community spirit building, but somehow there is a feeling of a place that could be very pleasant to live in.
Greek Street boarded up

Further north along the eastern side Hawthorn Avenue the work is much less well advanced. Some streets have been partly demolished and others are boarded up ready for demolition. Sadly there are a few people who have refused to leave their homes yet and are living in tiny islands surrounded by derelict houses.

To the western side of Hawthorn Avenue little remains of the old buildings with new buildings steadily going up, again in a mixture of styles. I have marked the areas boarded up as brownfield until construction starts. This does currently include the few houses still occupied, but I suspect not for long.

We also took a look at the old Hull FC rugby league ground, the Boulevard. The main entrance lies off Airlie Street, hence the team was nicknamed the Airlie Birds. They moved to share the KC stadium with Hull City football club in 2003. The old ground was used for greyhound racing for a while but now construction is under way for a new school, The Boulevard Academy. I wonder if they will have any rugby league teams?

Watch the video: Fuzzy Tolerance Screencast #12 - TileMill Part 2 (October 2021).