Benchmarking 2010/How to get some sample data
How to download sample data
The datasets will require some time to be merged and prepared, and the simbology still isn't fully decided on. In the meantime, you can download some sample data by following these steps:
- This is the website where the Spanish National Mapping Agency publishes some datasets
- On the top of the page, hit the Welcome link to enter the english version of the page
- Register for a new user. You'll need to enter the desired username, password, repeat password, full name and surname, email, and solve a captcha.
- Enter your account details to log in.
- Go to Advanced search
- In the "products" drop-down menu, select either BCN25-BTN25 for vector data, or Ortofoto PNOA Máxima Actualidad for aerial imagery.
- In the "MTN50 sheet number", enter any number between 1 and 1108.
- Barcelona is 420-421; Madrid is 559. You may want to check a sheet reference (caution: sheet reference is a 17MB image)
- Hit "See list of products". Select a file to download. You will see the license for the data, which boils down to "do not make any commercial use of this data" and "say that the data comes from the IGN"
- You will see a survey. Hit "No enviar y continuar con descarga"
- Hit "Click here yo begin download"
Raster data issues
Remember that the baseline of the OSGeo Benchmark for raster data are GeoTIFF files, but note you can only download ECW files. We will be converting the ECWs to GeoTIFFs.
There will be one big file for each one of the sheets in the following diagram:
Vector data issues
Once unzipped, a sheet of vector data contains lots of shapefiles. The shapefiles will be merged, and most probably only the most interesting themes will be used.
Please note that the shapefiles are in ETRS89 + UTM28N/29N/30N/31N. The final shapefiles will be in WGS84, so you're encouraged to reproject them if you think it's neccesary for your testing.
A letter after the theme code explains what kind of geometry the shapefile contains. P stands for Point; L stands for Line; S stands for Surface (Polygon).
|Code||Theme||How should it be rendered|
|0101L||Administrative Boundary||Depends on field TIPO_101, different kinds of dashed line|
|0107S||National park||2px dark green border with light green fill|
|Elevation & contour|
|0201L||Contour lines||Depends on field CATEG_201, 1px light or dark brown line|
|0204P||Elevation measured point||Label with field COTA_204|
|0207L/0207S||Elevation discontinuity: cutting, embankment, scree|
|0301L||River||3px blue line, label with field ETIQUETA|
|0304L||Canal||1px blue line, with flow arrow|
|0316S||Lake||2px blue line for border, light blue fill|
|0501S||Settlement||Light grey fill, rendered under any other features|
|0516S||Place of worship|
|0522S||Cemetery||Fill with symbol pattern|
|0528L||Wall/fence||1px black line|
|0555L/0555S||Historic building||Pinkish fill|
|0601L||Motorway||4px yellow line, with 1px red casing and 1px centerline|
|0604L||Road||3px orange, green or yellow line (depends on CFUN_0604 field) with 1px black casing|
|0607L||Motorway/road link||Depends on TIPO_0607 field: 2px red, orange, green or yellow line with 1px black or red casing.|
|0610L||Track||1px dashed brown line|
|0617P||Road Milestone||3px black circle; label with field ETIQUETA|
|0620L||Street||1px grey line|
|0623L||Path||1px dashed black line|
|0626L||Footway||1px dashed red line|
|0629L||Cycleway||1px dashed blue line|
|0638L||Hi-speed rail||3px black line, with "X" on it ----X----|
|0641L||Conventional rail||3px black line|
|0644L||Special rail||3px black line, with vertical lines on it|
|0653S||Rail Milestone||5px circle, label with field ETIQUETA|
|0665S||Airport Apron||Light pink; symbol at centroid.|
|0701L||Fuel pipeline||1px Dashed black-and-yellow line|
|0710L||Power line||1px Dashed red-and-black line|
|0713S||Power plant||Dark grey fill|
|0719S||Power substation||Dark grey fill|
|Toponyms & extra|
|0801P||Toponym w/o geometry||Label with field ETIQUETA|
|0802P||Toponym w/ geometry||Label with field ETIQUETA|
|0803L||Mountain range toponym||Label with field ETIQUETA|
|1001P||Geodetic survey/triangulation point||Triangle with dot in center|
This is by no means neccesary, but you might receive a penalty* if your rendering hits any of the following common pitfalls:
- Overlapping labels. Your software has text collision detection, hasn't it?
- Labels on linear features (e.g. river names) should follow the line geometry. Every letter tilted at the same angle = failure.
- Rendering any road casing on top of any road fill.
* The penalty is that Iván will not buy you a beer during FOSS4G. See, this is a friendly competition, but we can play rough :-P
In an ideal world where money grows on trees and the streets are made out of candy, the development teams should have unlimited time to work on the map rendering.
Ideally, the rendering should be the same as the official topographic maps. You can download samples from the IGN (just follow the above instructions, but select MTN25RASTER instead of BCN25/BTN25).
As you may see, the rendering rules can become very complex, and be non-intuitive at first. This is a performance benchmark, not a beauty one, so teams should focus on performance, and not pixel-to-pixel accuracy.
For reference, the legend of the topo map looks like this: