nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Vehicle placement on CityEngine-generated streets.

JoshWade

Hello again 🙂

I am beginning to create driving scenarios for a driving simulator. (For example, on a highway you are traveling at 70mph when suddenly the vehicle in front of you applies the brakes hard). I see that CE uses some mechanism for placing the cars on the roads neatly between the lines (Even on curved roads).

I am hoping that I can use your algorithm for my AI-driven cars. I assume it has something to do with the street network edges as well as the particular attributes of the street?

Any help would be wonderful!

-Josh

Finde mehr Beiträge mit dem Tag

Accepted answers

MatthiasBuehler1

edit the code around line 240 :

1] note the MakeLaneMarkers shape copy after the Vehicles().
2] add the code for the marker creation and position reports

Streetsides -->  case calcNbrOfLanes < 1.1 : Asphalt  case Nbr_of_left_lanes == 0 && Nbr_of_right_lanes == 0:   split(v,unitSpace,0){ ~calcLanesLeft    : Lanes(calcNbrOfLanes,connectionEnd,0) Vehicles(0) MarkerCreation("left")        | Median_width      : Median        | ~calcLanesRight   : scaleUV(0,-1,-1) Lanes(calcNbrOfLanes,connectionStart,2) Vehicles(2) MarkerCreation("right") }  else:   split(v,unitSpace,0){ ~Nbr_of_left_lanes : Lanes(Nbr_of_left_lanes,connectionEnd,0) Vehicles(0) MarkerCreation("left")        | Median_width      : Median        | ~Nbr_of_right_lanes : scaleUV(0,-1,-1) Lanes(Nbr_of_right_lanes,connectionStart,2) Vehicles(2) MarkerCreation("right")}  @Range ( "all", "left", "right") @Group("MARKERS") attr markerOutput = "all"  MarkerCreation(side) -->  case markerOutput == "all" :   MakeLaneMarkers  case markerOutput == side :   MakeLaneMarkers  else :   NIL  MakeLaneMarkers -->  color(1,0,0)  t (0,.1,0)  split(v,unitSpace,0) { ~Lane_width : LaneShape }*  LaneShape -->  split(v,unitSpace,0) { ~1 : NIL | markerDim : LaneCenterLine | ~1 : NIL }  markerDim = 0.25 markerDist = 15  LaneCenterLine -->  split(u,unitSpace,0) {{ markerDim : LaneMarker | ~ markerDist : NIL }* | markerDim : LaneMarker }  LaneMarker -->  report("markerPosX", convert(x, scope, world, pos, 0.5 * scope.sx, 0.5 * scope.sy, 0.5 * scope.sz))  report("markerPosY", convert(y, scope, world, pos, 0.5 * scope.sx, 0.5 * scope.sy, 0.5 * scope.sz))  report("markerPosZ", convert(z, scope, world, pos, 0.5 * scope.sx, 0.5 * scope.sy, 0.5 * scope.sz))  X. # NIL

Now once you generate a street, you should get the reports in the Inspector's Reports tab.

To grab those and produce your java script code :
1] copy the attached .py script to your scripts folder
2] run the Script Based Exporter ( Python ), where you select the new script under the Misc options, then run it.
3] open the console ( Python output ) and get your code.

To adapt the offset, just copy paste your export offset values and edit the Python script accordingly.

I also just added the lane direction switch called (markerOutput).

Note also that now, the markers are produced as geometry, thus you may want to NIL it as commented out in the last line after the reports ( X. # NIL )

let me know if it works on your machine too. 😉

markerInstances.py.zip

All comments

JoshWade

Thank you very much! This has been extremely helpful.

MatthiasBuehler1

got it. as assumed.

was a missing

i += 1

here's the new file !

markerInstances.py.zip

JoshWade

No worries 🙂 I will take a look as well to see if I can find it.

MatthiasBuehler1

hmm. I did not test it that thoroughly.

but I assume there's a little issue with the indices in the loop which grabs the corresponding coordinates.

I guess I'd be faster debugging this than you, so I'll try to find the issue.

sry for that .. I'm not a developer .. 🙂

JoshWade

Matthias,
I'm looking at the output more closely now and I'm confused about something. Why are there several markers with the same coordinates, but with different id's? In the example that you posted above, the same thing occurs.

What does it mean?

JoshWade

Okay, It seems to be working now! Thank you for your help with this. I will let you know if I have any problems.

MatthiasBuehler1

edit the code around line 240 :

1] note the MakeLaneMarkers shape copy after the Vehicles().
2] add the code for the marker creation and position reports

Streetsides -->  case calcNbrOfLanes < 1.1 : Asphalt  case Nbr_of_left_lanes == 0 && Nbr_of_right_lanes == 0:   split(v,unitSpace,0){ ~calcLanesLeft    : Lanes(calcNbrOfLanes,connectionEnd,0) Vehicles(0) MarkerCreation("left")        | Median_width      : Median        | ~calcLanesRight   : scaleUV(0,-1,-1) Lanes(calcNbrOfLanes,connectionStart,2) Vehicles(2) MarkerCreation("right") }  else:   split(v,unitSpace,0){ ~Nbr_of_left_lanes : Lanes(Nbr_of_left_lanes,connectionEnd,0) Vehicles(0) MarkerCreation("left")        | Median_width      : Median        | ~Nbr_of_right_lanes : scaleUV(0,-1,-1) Lanes(Nbr_of_right_lanes,connectionStart,2) Vehicles(2) MarkerCreation("right")}  @Range ( "all", "left", "right") @Group("MARKERS") attr markerOutput = "all"  MarkerCreation(side) -->  case markerOutput == "all" :   MakeLaneMarkers  case markerOutput == side :   MakeLaneMarkers  else :   NIL  MakeLaneMarkers -->  color(1,0,0)  t (0,.1,0)  split(v,unitSpace,0) { ~Lane_width : LaneShape }*  LaneShape -->  split(v,unitSpace,0) { ~1 : NIL | markerDim : LaneCenterLine | ~1 : NIL }  markerDim = 0.25 markerDist = 15  LaneCenterLine -->  split(u,unitSpace,0) {{ markerDim : LaneMarker | ~ markerDist : NIL }* | markerDim : LaneMarker }  LaneMarker -->  report("markerPosX", convert(x, scope, world, pos, 0.5 * scope.sx, 0.5 * scope.sy, 0.5 * scope.sz))  report("markerPosY", convert(y, scope, world, pos, 0.5 * scope.sx, 0.5 * scope.sy, 0.5 * scope.sz))  report("markerPosZ", convert(z, scope, world, pos, 0.5 * scope.sx, 0.5 * scope.sy, 0.5 * scope.sz))  X. # NIL

markerInstances.py.zip

MatthiasBuehler1

hi !

it uses a distance attribute, thus places markers approximately that distance apart from each other. this example just produced 4.

I'll wrap up the code and post here.

JoshWade

😄 Excellent! Thank you, this seems exactly what I need. And I will be able to run this Python script on my street network (maybe twice for differentiation between left and right lanes) to generate the appropriate points, correct?

I will be centering the points according to Unity's origin. This probably will not be an problem: I can write a script to modify the values according to the level of displacement that occurs.

The example that you have shown me produces 4 points per lane. Will I be able to modify that value if necessary to something higher or lower?

MatthiasBuehler1

so that'd be the result of what CE produces for the markers :

1 street segment with 3 lanes, 4 marker points per lane ( 12 in total )

instantiateMarker ( 820207.073822,9.48134291172,-72516.0204315,0);
instantiateMarker ( 820207.073822,9.48134291172,-72516.0204315,1);
instantiateMarker ( 820207.073822,9.48134291172,-72516.0204315,2);
instantiateMarker ( 820207.073822,9.48134291172,-72516.0204315,3);
instantiateMarker ( 820207.073822,9.48134291172,-72516.0204315,4);
instantiateMarker ( 820207.073822,9.48134291172,-72516.0204315,5);
instantiateMarker ( 820207.073822,9.48134291172,-72516.0204315,6);
instantiateMarker ( 820207.073822,9.48134291172,-72516.0204315,7);
instantiateMarker ( 820207.073822,9.48134291172,-72516.0204315,8);
instantiateMarker ( 820207.073822,9.48134291172,-72516.0204315,9);
instantiateMarker ( 820207.073822,9.48134291172,-72516.0204315,10);
instantiateMarker ( 820207.073822,9.48134291172,-72516.0204315,11);

now I assume you run your general CE exports with the offset correction to center the dataset around the cartesian origin in Unity. Once you know that XZ offset, this could be subtracted from the results which you get by the reports.

of course you could run this twice, once just for the right lanes, once just for the left lanes. 🙂

let me know what you think so far.

JoshWade

Thanks for all your help so far, by the way!

Here is a potential class definition for a Marker object:

public class Marker {
     /* MEMBER DATA */
     public var m_vector : Vector3; //coordinates
     public var m_id : int; //unique id for each marker

}

Then this function (effectively a constructor) might be applicable:

function instantiateMarker ( x : float, y : float, z : float, id : int) {

     var markerObj : Marker;
     markerObj = new Marker();
     markerObj.m_vector = new Vector3(x,y,z);
     markerObj.m_id = id;

}

MatthiasBuehler1

ah, sorry, yes.

With Python, I can directly create the JavaScript code ( basically just a text output ) which creates the code you quoted, looping over all markers CE finds.

when you can post 1 example that runs with the correct syntax ( e.g. vector definition ), I can make the code generic and directly feed the positions.

JoshWade

When you say to find a line of code to create the marker, do you mean on the Unity side of things? I suppose it would depend on how the street marker data was created/stored. If the markers were each individual gameObjects, then something like the following could be used to instantiate Vector3 objects at each marker: (JavaScript)

      var marker : Vector3; //vector to hold xyz points of marker
      marker = transform.Find("marker_id#").position; //supposing that street markers each have a unique id

Once all of the necessary markers have been instantiated, they can be used by iTween for path following.

MatthiasBuehler1

cool so far then.

I guess we're faster if I quickly write the code down, then pass the stuff on for refinement.

can you find me a line of code which creates such a marker via code ?

pseudo code :

putStreetMarker(x,y,z)

then I could create directly the text you can run which produces all markers for you.

let me know ..

JoshWade

Yes! 😄 This is fantastic. If I am able to successfully produce corresponding points in Unity using these markers, then this is exactly what I need. I can figure out some way to determine direction and network connectivity later on.

What shall I do in terms of Python and creating these markers?

MatthiasBuehler1

I've played a little with the Philly code to produce some visible markers on the lanes.

what you could do now is report those positions and create some script code for UNITY ( BOO / JScript ) that produces your markers in all those locations.

Though the driving direction and the precise linking of lanes over the crossroads must be done manually, or if possible within that system you use. CE cannot really help there efficiently.

Let me know what you think.

matt

ps. of course you can get the code, but let's first find the workflow.

lanemarkers.jpg

JoshWade

I have Advanced 64 Bit (2011.2) for Windows 7 OS. The example I'm using is the Philadelphia model (4 copies to create one very large version, but with different rule file attributes to create variation). The street network has been modified slightly in the original section of the city, but the networks in the surrounding quadrants are entirely different.

MatthiasBuehler1

- are you using the modern streets example for your street models ?
- which version of CityEngine do you have ? Advanced ( PRO ) ?

because you need Python Scripting to write that metadata out.

lemme know.

JoshWade

Hello 🙂

Yes that is correct. I just need to know the coordinates of the nodes the street. I assume that I can create 'lanes' via displacing the nodes in the path in some direction or another.

How do I go about finding/accessing/utilizing these markers?

-josh

MatthiasBuehler1

hi !

so you just need the position of those nodes and the curve network is created by that iTween system ? did I understand this correctly ?

because if that's the case, your main task is 'just' to report those markers, which is not too hard in CE.

lemme know. 🙂

JoshWade

Thanks for the reply!

I have begun to incorporate the Unity plugin called iTweens into my project. It requires an array of nodes (which are just 3d vector coordinates x,y,z). I would like to dynamically create nodes along the street that are properly on and above the street so that my AI car can drive on it.

These nodes would form a path (even on curved streets) which would then be stored in an array to be used by iTweens.

MatthiasBuehler1

hi !

the vehicles are actually placed 'geometrically'. for this, the streets are split according to their UV coordinates. First into lanes and medians, then into smaller segments, on which the cars are inserted.

at the current state, CityEngine has no actual lane information available to work with. Thus, all cars you see are simply placed 'randomly'.

for a driving simulator, what you could do is 'create some metadata' which lets you recreate the curve network for use in your simulator, using Python scripting.
but for this, I'd of course need to know what your simulator needs as input data.

Nimm an der Unterhaltung teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.