d-wasserman / complete_street_rule Goto Github PK

Signal placement and traffic control generally need to be revamped. They might need to be placed in areas that make less sense for single cross-section locations, but a reversal switch might be enough to enable cross-sections with the current approach.

Similar to bridge piers, the lamps also overlap with the bridges above.

I tried to add an empty bounding box by extrude(y, 6.5) to test whether the lamps overlap with the bridges above.

Sidewalk_Lamp(offset) -->
	alignScopeToGeometry(yUp,largest,0)
	alignScopeToAxes(y)
	center(xz)
	r(0,90,0)
	s(0,0,0)
	report("Objects.Street Lamp Count", 1)
	extrude(y, 6.5)
	Lamp_Check(offset)

Lamp_Check(offset) -->
    case overlaps(inter):
        NIL
    else:
        Lamp_Asset(offset)
    
Lamp_Asset(offset) -->
	t( SLight_Translate_X ,0, SLight_Translate_Z )
	r(0,90,0)
	t(offset,0,0)
	set(material.name,"Street_Lamp")
	label("Street Lamp")
	color( _ThematicRouter ("Pedestrian","lamp"))
	i(Street_Lamp_Object)
	Delete_Texture

However, it sometimes changes the orientation of the lamps, i.e. some lamps are not in the correct orientation, as shown in the figure below

How to solve the problem?

Hi there,

I noticed this growing trend in Urban Design lately of having the bike lanes as part of the sidewalk (see diagrams)

Bike lane on sidewalk, planting near the buildings:

Bike lane on sidewalk, planting near the street:

Would be possible to implement such a feature to the Complete Street Rule in the near future?

Thank you!

The best fit setting was intended to be an abstraction of width by adding width to drive lanes when there is "extra" space (more than the lane width). However, if there are zero lanes, the setting reacts by consuming all the geometry on the road. This can be fixed by just going off of best fit to exact, but that is not a great solution for users (especially anyone doing demos). This will be taken care of ASAP. There is a short term and long term fix I have in mind.

As shown in the figure below, the yellow centerline is not created for the selected crossing.

This is a general comment that I would appreciate any donations from individuals using this rule of of open source models, textures, and assets to improve the visual quality of the rule. Also any recommendations can be left as a comment on this issue.
Some general elements that need consideration for an overall are:

• Removal of stamp based textures to only use full PBR materials. This means stamps would be replaced with inserted "stencils" for bike lanes, turn lanes, bus lanes, TWLTLs, etc.

• Bike Lane Symbols (in Dev Branch)

• Bike Lane Arrows (in Dev Branch)

• Bus Lane Letters (in Dev Branch)

• TWLTL Arrows (in Dev Branch)

• TWLTL Transition/Painted Taper (Similar to that documented here) (in Dev Branch)

• HOV Symbol (in Dev Branch)

• Turn Lane Arrows (Multiple- Right, Right Through, Through, Left Through, Left, All) (in Dev Branch)

• Carshare Only Symbol (in Dev Branch)

• Bus Stop Letters (in Dev Branch)

• Stop Symbol (in Dev Branch)

• Crossing hatch (in Dev Branch)

• Angled Parking (in Dev Branch)

• Bike Buffer Paint Marks (In Dev Branch)

• Micromobility Parking Spots (in Dev Branch)

• Acquisition of PBR textures for the bare minimum of:

• Painted Asphalt (White, Yellow, Green, Red, Blue - Edits were made in GIMP to the selected Asphalts below. )

• Asphalt (Black or Black-Grey)

• Concrete (Sidewalks)

• Brick/Stones (Sidewalks/Crossing) - Multiple (1,2,3,4,5,6)

• Curb/Planting Borders (Edited Concrete)

• Dirt (Ground)

• Grass (Plantings)

• Rumble Strips (Use Asphalt for now)

• Rail/General Metal Textures (Rails)

• Acquisition of New Street Assets - current CityEngine upgrades suffice for now. Identifying unreal replacement actors/assets might be a good way to address this generally instead of keeping them with the project.

Notes:

• Concerns over size- as I mentioned these upgrades to outside parties, there were concerns about the size of these changes. It could increase the repos size enough it is harder to download. As it stands the repo is ~130 MB, and the upgrade max target is ~250 MB. This is an increase in size, but not massive. Experiments with GIMP exports of JPGs show that reducing the quality of the export to 90-95% can decrease the size of the file substantially. This will be used strategically to make sure PBR upgrades can be done quickly and efficiently. After that if someone exports to Unreal or other platform, at least material replacements will be substantially easier.

The traffic lights can not be hidden even though I set traffic lights to None.

This is just a quick write up on something that has been observed on a few occasions. Generally, the Complete Street rule and some of the other rules using UV space 0 (absolute geometry texture space), seem to have weird reactions to large curb radii at intersections. It seems like the street shapes are wider than the street width parameters are communicating. A work around is adjusting the crosswalk and crosswalk-stop bar gap attributes so that the widen transition shapes do not interact with the rest of the splits on the street, but I can't narrow down why this is exactly occurring. If anyone has screenshots or parameter lists that they try for replication I would appreciate the insight.

Hi David,

A possible enhancement to put on the wish list:

When using CE streets to create pedestrian paths, the usual trick is lowering down the street width to 0.
This way we end up with just two contiguous sidewalk segments.
However, when we try to do this applying the CSR, we can't get an homogeneous result because of the concrete curbs that are always set at the sidewalk limit (see screenshots).
Would it be possible to add an attribute to get rid of the curbs when not needed?
In my opinion, best would be an option to decide if we want to have right, left or both curbs for each sidewalk.

Roundabouts UV mapping doesn't look right both in CE and UE

Hi!

The cyclist assets from https://github.com/d-wasserman/Complete_Street_Rule/tree/master/assets/Complete_Streets/LowPolygon3D.com_Cyclists have issues when exporting for example to Blender via FBX or Unreal via Datasmith.

See:

The issue is that the inside and the outside of the models are separate geometry. This will lead to artifacts for example in Unreal as Opaque geometry is rendered two sided (what you see on the screenshot is actually the backside of the inside of the model).

This could be fixed by removing the "internal" faces and readjusting the normals in Blender.

I have recently been looking more and more at connecting segments and short segments as part of cross sections. These segments occur as a result of imported data, and even specific design choices made early on when the rule was being created that were essentially given easy solutions to clearly very specific problems. Future plans include changing the rules reaction to Stop_Begin and Stop_End parameter defaults at "none", and specifically how the rule treats short streets. Work in progress.

It seems that "One Way Street" is not supported by the Complete Street Rule.
Do you have a plan to support it?

I read the instructions on the ESRI vegetation library but I am unsure how to connect the two data bases.....3d plant library/lumenrt in my assets folder but still not good. How do I tell complete streets to go find the trees for my sidwalks?

In the “Median Plantings” section, there is no Median_Tree_2_Height input (see attached screenshot)

As shown in the figure below, the generated bridge piers intersect with the streets below.
How to solve the problem?

hello~
I find a question while using this rule,stop markings will be Covered by crosswalk markings while two road angle is too small. Can you help me ?
thanks

• Thomas Fuchs at Esri noticed that some of the textures are 8 bit depth textures that don't work with SLPKs.

• Other request at Esri identified a need to change some paths to update the Complete Street Example for 3D models.

Both of these requests will likely warrant a new version number.

Changing attribute "Traffic Direction" has no impact on traffic light's position.
This might be a problem for projects located in left-hand traffic countries.

Both Freeway and FreewayEntry start rules don't allow any population with vehicles

On-Street Parking section, Right/Left_Parking_Type: Parallel with Curbside Bus Stop
The BUS writing on the street is mirrored. Is there a particular reason for that?
In case it's not intentional, I guess it should be easy to fix.

I hope the author can add guardrails on both sides of the road to the rules

There is a issue with the textures and the rule that are creating unexpected results in Nvidia Omniverse.