< AND Data

AND Data/Import Floris

Development of this script has stopped because I'm now also focussing on Marc's C script, which is probably more scalable

This is a list of AND road tags and values I've used in my import script.

Suggestions from Mapping ANDs Tagging Scheme to OSMs Tagging Scheme are mostly implemented.

All nodes, segments and ways have a source=florisANDimport_1 tag.

Roads file

FieldAND descriptive nameFormatIDDescriptionImplemented?
RD_1RD_IDN8ID of roadsexternal-id=15800465
RD_2N20Used for compatibility with AND format, always ‘0’ignored
RD_3RD_LENGTHN5Road length in hectometersignored
RD_4RD_DIRECTIONN1Permitted Traffic Flow
0Traffic allowed in both directionsignored
1Traffic allowed from RD_ID_FROM to RD_ID_TOoneway=yes
2Traffic allowed from RD_ID_TO to RD_ID_FROMoneway=-1
RD_5RD_TYPEN2Road classification
1Motor wayhighway=motorway
2Federal highway dual carriage way (motor way characteristics)highway=trunk
we'll have to see which roads have this class
3Federal highwayhighway=primary
4Regional roadhighway=secondary
5Local roadhighway=tertiary
6Other roadhighway=unclassified
if RD_21=-1 then highway=pedestrian
7Ferry (cars and cargo)route=ferry
motorcars=yes
hgv=yes
9Train ferry (passenger and/or cargo)route=ferry
motorcars=no
foot=yes
30Railway, passenger and/or freight transportrailway=rail
50Link to airports, railway stationshighway=service
58Walking connection between Railway stationshighway=footway
59Virtual connection. Used to connect features in the data that are not linked by any other defined features in the databaseno data yet with this tag
RD_6RD_NATIONN3Nation code (table is available _c.lst file)ignored
RD_7RD_LEVELN2Connection level. The connection level of a road expresses the importance of that road. The general classification is as follows:ignored for now, we could do a check to see if there aren't any highway=unclassified with RD_LEVEL=0 (for example)
0E-roads in Europe
1Important national roads in such a way that all type 10 to 13 locations are connected.

Scale around 1 : 4,000,000

2Secondary roads in such a way that all type 10 to 14 locations are connected.

Scale around 1 : 2,000,000

3Through roads in such a way that all type 10 to 15 locations are connected.

Scale around 1 : 1,000,000

4Local connector roads in such a way that all type 10 to 16 and 20 to 26 locations are connected.

Scale around 1 : 500,000

5Other roads

Scale around 1 : 250,000

6All other roads (streets)
10All railways
RD_8RD_DELETEDLAND Internal Codeignore
RD_9RD_SLOWC1CSlow road type (road within city limits)ignored (primary roads also have this tagged)
RD_10RD_NAMEC60Road (street) namename=streetname
RD_11RD_CODE_NAT1C12National road numberref=NAT1
RD_12RD_CODE_NAT2C12National road numberref=NAT1;NAT2
RD_13RD_CODE_NAT3C12National road numberref=NAT1;NAT2;NAT3
RD_14RD_CODE_INT1C12International road numberint_ref=INT1
RD_15RD_CODE_INT2C12International road numberint_ref=INT1;INT2
RD_16RD_CODE_INT3C12International road numberint_ref=INT1;INT2;INT3
RD_17RD_TUNNELLTunnel flagtunnel=yes
layer=-1

layer not set if RD_FLOOR is set
RD_18RD_TOLLLToll flagtoll=yes
RD_19RD_TIMEN5Ferry journey time in minutes
RD_20RD_FLOORN1Relative height to a crossing feature

1 is below 2 is below 3 etc.
9 if relative height is unknown.

ignored for now, because there's no height difference on Texel, should be layer=...
RD_21RD_TONNAGEN3Tonnage admitted on ferry
-1Only passengers (ferries) – Also used for pedestrian streets/ virtual connectionsused in RD_5
if RD_5=6 and RD_21=-1 then highway=pedestrian
3max. 3.5 metric tonsmaxweight=3.5
28max. 28 metric tonsmaxweight=28
40max. 40 metric tonsmaxweight=40
99> 100 tonsmaxweight=100
i think this will be sufficient for almost all hgv
RD_22RD_TOLL_CARGOLToll (for trucks only) flagtoll=hgv
RD_23RD_OTHERC60Other Attributes:
Sr#1Slip road segment
Rb#1Roundabout segment
Lb#1Lay-by segment
4wd#1Four wheel drive road segment
Unsealed#1Unsealed road segments
Fc#[0-4]Functional road class 0 to 4
Lh#1Long haul
Stub#1Stub link
hn#Housenumber range

L : left, direction from FNODE_ to TNODE_
R: right, direction from FNODE_ to TNODE_
E: even
O: odd
M: mixed
e.g. hn#LE2-12#RO1-11

ignored
but very cool :)
RD_24RD_PROVN3Province code (table is available _p.lst file)ignored
RD_25RD_CITY_IDN11City code of link (link to ND_ID)ignored
RD_26RD_MUN_IDN11Municipality code of link (table is available _m.dbf file)ignored
FNODE_FNODE_N12From node ID of linkignored
TNODE_TNODE_N12To node ID of linkignored
This article is issued from Openstreetmap. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.